Triple
T8294774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City Stadium |
E194186
|
entity |
| Predicate | usedAsHomeFieldUntil |
P30600
|
FINISHED |
| Object | 1956 |
—
|
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: 1956 | Statement: [City Stadium, usedAsHomeFieldUntil, 1956]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsHomeFieldUntil Context triple: [City Stadium, usedAsHomeFieldUntil, 1956]
-
A.
homeFieldSince
Indicates that a particular location has served as the designated home field or home venue for an entity starting from a specified point in time.
-
B.
previousHomeFieldYears
Indicates the years during which a particular location previously served as the home field for an entity (such as a team or organization).
-
C.
usedAsHomeCourtOf
Indicates that a particular venue or location serves as the primary home court where a team or individual regularly hosts its games or matches.
-
D.
formerHomeStadium
Indicates that a venue previously served as the home stadium for a team or organization but no longer holds that status.
-
E.
playedHomeGamesUntil
chosen
Indicates the period up to which a team or player hosted their home games at a particular venue.
- 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_69ca82e50ebc81909aa7b260c76bd757 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7df5fff88190ac51a8d1c3eb2fe2 |
completed | March 31, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:52 p.m.