Triple
T11821649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Football Stadium at Windsor Park |
E281150
|
entity |
| Predicate | mainStand |
P50008
|
FINISHED |
| Object | South Stand |
—
|
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 Stand | Statement: [National Football Stadium at Windsor Park, mainStand, South Stand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainStand Context triple: [National Football Stadium at Windsor Park, mainStand, South Stand]
-
A.
mainStandName
chosen
Indicates that one entity is the primary or official name of a stand associated with another entity.
-
B.
homeStandOf
Indicates that a particular venue or location serves as the primary home stadium or home ground for a sports team or organization.
-
C.
mainRite
Indicates that one ritual, ceremony, or rite is the primary or central rite associated with a given context, entity, or event.
-
D.
traditionalHomeStand
Indicates that an entity plays or hosts its home games at a venue considered its traditional or long-standing home location.
-
E.
baseStandard
Indicates that one entity serves as the foundational or reference standard upon which another entity is defined, measured, or evaluated.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5e9c50481909b2287a0b23d2094 |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.