Triple
T18700091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bonatti Pillar |
E457223
|
entity |
| Predicate | faceOrientation |
P40589
|
FINISHED |
| Object | west face |
—
|
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: west face | Statement: [Bonatti Pillar, faceOrientation, west face]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: faceOrientation Context triple: [Bonatti Pillar, faceOrientation, west face]
-
A.
surfaceOrientation
chosen
Indicates the spatial orientation or facing direction of a surface relative to a reference frame or viewpoint.
-
B.
functionalOrientation
Indicates a relationship where an entity is characterized by the specific function, role, or operational purpose it is oriented or designed to fulfill.
-
C.
orientationType
Indicates the specific kind or category of orientation relationship that exists between entities (such as spatial, directional, or alignment-based orientation).
-
D.
gazeDirection
Indicates the direction in which an entity is looking or focusing its visual attention.
-
E.
sessionOrientation
Indicates the directional or spatial alignment relationship established between entities within a session or interaction context.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562eb06b481908ef9efdb976008f3 |
completed | April 19, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.