Triple
T5257352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Wall |
E118733
|
entity |
| Predicate | angleBetweenWalls |
P62552
|
FINISHED |
| Object | 125 degrees |
—
|
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: 125 degrees | Statement: [The Wall, angleBetweenWalls, 125 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: angleBetweenWalls Context triple: [The Wall, angleBetweenWalls, 125 degrees]
-
A.
pyramidAngle
Indicates that there is a specified angular relationship between elements (such as faces, edges, or apex and base) of a pyramid-shaped structure.
-
B.
cornerOfTriangle
Indicates that the subject is a vertex (corner point) belonging to a specific triangle.
-
C.
wallFeature
Indicates that one entity functions as a structural or design feature associated with a wall of another entity.
-
D.
hasWallShape
Indicates that an entity possesses a wall whose form or outline matches a specified geometric or structural shape.
-
E.
hasSideWalls
Indicates that an object or structure possesses side walls as part of its physical configuration.
- F. None of above. chosen
Provenance (4 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_69bd446978108190bb5f9c5c23d93f88 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bcced6881909bdb7ac5471a37fe |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd7bcabe58819096255672664513b1 |
completed | March 20, 2026, 4:54 p.m. |
Created at: March 20, 2026, 1:50 p.m.