Triple
T24897514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ponsford Stand section |
E623185
|
entity |
| Predicate | locatedOnSideOfStadium |
P125276
|
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: [Ponsford Stand section, locatedOnSideOfStadium, southern side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnSideOfStadium Context triple: [Ponsford Stand section, locatedOnSideOfStadium, southern side]
-
A.
hasStadiumSide
chosen
Indicates that one entity is located on or corresponds to a particular side or section of a stadium in relation to another entity.
-
B.
situatedOnSideOf
Indicates that one entity is located along or beside the lateral part or edge of another entity.
-
C.
relativePositionInStadium
Indicates the spatial relationship between entities based on where they are located relative to each other within a stadium.
-
D.
locationSide
Indicates that one entity is positioned on a particular side (e.g., left, right, front, back) relative to another entity or reference point.
-
E.
locatedInStadium
Indicates that an entity is situated within or at the premises of a specific stadium.
- 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_69e2fac597708190a922bf39a49ec70a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 18, 2026, 5:26 a.m.