Triple
T33007747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Stand |
E844555
|
entity |
| Predicate | standOrientation |
P186979
|
FINISHED |
| Object | south |
—
|
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: south | Statement: [South Stand, standOrientation, south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standOrientation Context triple: [South Stand, standOrientation, south]
-
A.
standConfiguration
Indicates that one entity specifies or defines the arrangement, setup, or layout configuration of a stand (e.g., booth, display, or support structure) in relation to another entity.
-
B.
styleOrientation
Indicates the general stylistic direction or aesthetic approach that characterizes how something is designed, presented, or expressed.
-
C.
legOrientation
Indicates the relative positioning or directional alignment of an entity’s leg(s) with respect to a reference frame or another object.
-
D.
armOrientation
Indicates the spatial direction or angle at which an arm is positioned relative to a reference frame or body.
-
E.
sessionOrientation
Indicates the directional or spatial alignment relationship established between entities within a session or interaction context.
- 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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb2e9309fc81909dfefd9020d6fbad |
completed | May 6, 2026, 12:05 p.m. |
Created at: May 1, 2026, 1:23 a.m.