Triple
T37080284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barbour Fields area |
E918124
|
entity |
| Predicate | hasAssociatedStadium |
P5119
|
FINISHED |
| Object | Barbourfields Stadium |
—
|
NE NERFINISHED |
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: Barbourfields Stadium | Statement: [Barbour Fields area, hasAssociatedStadium, Barbourfields Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedStadium Context triple: [Barbour Fields area, hasAssociatedStadium, Barbourfields Stadium]
-
A.
associatedStadiums
Indicates that there is a relationship linking an entity to one or more stadiums with which it is connected or affiliated.
-
B.
hasTeamStadium
Indicates that a sports team is associated with or plays its home games at a particular stadium.
-
C.
associatedWithStadiumLocation
Indicates a relationship where an entity is connected or linked to the location of a specific stadium.
-
D.
hasEmployerStadium
Indicates that an organization or employer is associated with, owns, or primarily uses a particular stadium.
-
E.
containsStadium
chosen
Indicates that a location or area includes a stadium within its boundaries or premises.
- 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_69f76e9952b88190a6fe01ba01476520 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: May 3, 2026, 4:14 p.m.