Triple
T28372478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Spider’s Web |
E718669
|
entity |
| Predicate | hasRockFaceOrientation |
P12663
|
FINISHED |
| Object | generally south-facing |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: generally south-facing | Statement: [The Spider’s Web, hasRockFaceOrientation, generally south-facing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRockFaceOrientation Context triple: [The Spider’s Web, hasRockFaceOrientation, generally south-facing]
-
A.
hasEastFace
Indicates that something has a side or surface that is oriented toward the east.
-
B.
hasFace
Indicates that one entity possesses, displays, or is characterized by a face.
-
C.
isFaceOn
Indicates that one surface or side of an object is oriented directly toward, or aligned to face, another object or reference direction.
-
D.
hasOrientation
chosen
Indicates that one entity is positioned or directed in a specific spatial or conceptual alignment relative to a reference frame or another entity.
-
E.
isOnFace
Indicates that one entity is located directly on the surface or face of another entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 28, 2026, 1 a.m.