Triple
T27536836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Athletics Championships |
E695119
|
entity |
| Predicate | typicalStadium |
P72058
|
FINISHED |
| Object | Alexander 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: Alexander Stadium | Statement: [British Athletics Championships, typicalStadium, Alexander Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStadium Context triple: [British Athletics Championships, typicalStadium, Alexander Stadium]
-
A.
typicalVenueStadium
chosen
Indicates that the usual or characteristic venue for the referenced activity, event, or entity is a stadium.
-
B.
stadium
Indicates that an entity is a sports or event venue where games, competitions, or large gatherings take place.
-
C.
mainStadium
Indicates that a particular stadium serves as the primary or home stadium associated with an entity (such as a team, club, or organization).
-
D.
keyStadium
Indicates that a stadium serves as the primary or main venue associated with a particular entity (such as a team, event, or organization).
-
E.
stadiumFor
Indicates that a particular stadium serves as the designated home or primary venue for a specific team, event, or organization.
- 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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69ffc704e1e88190884928a6a5c55a87 |
completed | May 9, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69ffc6b483d881908ad872e25fa6abc5 |
completed | May 9, 2026, 11:43 p.m. |
Created at: April 27, 2026, 1:29 p.m.