Triple
T5447452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olympia Stadium |
E122282
|
entity |
| Predicate | servedAsHomeArenaFrom |
P56462
|
FINISHED |
| Object | 1927 |
—
|
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: 1927 | Statement: [Olympia Stadium, servedAsHomeArenaFrom, 1927]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedAsHomeArenaFrom Context triple: [Olympia Stadium, servedAsHomeArenaFrom, 1927]
-
A.
formerHomeArena
Indicates that a venue previously served as the primary home arena for a team or organization but no longer holds that status.
-
B.
homeArenaAlternateName
Indicates that an entity’s home arena is known by an alternate or secondary name.
-
C.
homeArenaOfChampionTeam
Indicates that a particular arena serves as the primary home venue for a specified champion team.
-
D.
homeFieldSince
chosen
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.
-
E.
hasSportsTeamVenueFor
Indicates that a venue serves as the home or hosting location for a particular sports team.
- 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_69bd4640f52c81909e653ec361f66d76 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd95be329c81908783420cf81b6af5 |
completed | March 20, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69bd919e8d18819098c4af6a015e5cc2 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:07 p.m.