Triple
T37416043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Stand |
E929710
|
entity |
| Predicate | positionOnStadium |
P95425
|
FINISHED |
| Object | southern side |
—
|
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: southern side | Statement: [South Stand, positionOnStadium, southern side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnStadium Context triple: [South Stand, positionOnStadium, southern side]
-
A.
relativePositionInStadium
chosen
Indicates the spatial relationship between entities based on where they are located relative to each other within a stadium.
-
B.
positionInCourt
Indicates the specific role or standing an entity holds within a court setting or judicial proceeding.
-
C.
roleAtStadium
Indicates that an entity holds a specific role, function, or position associated with a particular stadium.
-
D.
positionInLineup
Indicates the specific ordered place an entity occupies within a lineup or sequence of entities.
-
E.
positionOnRace
Indicates the relative ranking or placement an entity holds within the context of a race or competitive event.
- 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_69f76ebde49481908566cd96b37ccc84 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffcc6182b48190afb598ced6500e66 |
completed | May 10, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69ffcbb363748190bc6f8d038fba44ff |
completed | May 10, 2026, 12:05 a.m. |
Created at: May 3, 2026, 4:16 p.m.