Triple
T27700109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Land Shark Stadium |
E698403
|
entity |
| Predicate | subsequentNameOfSameVenue |
P117400
|
FINISHED |
| Object | Sun Life 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: Sun Life Stadium | Statement: [Land Shark Stadium, subsequentNameOfSameVenue, Sun Life Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentNameOfSameVenue Context triple: [Land Shark Stadium, subsequentNameOfSameVenue, Sun Life Stadium]
-
A.
hasSuccessorVenueName
chosen
Indicates that one venue is followed or replaced by another venue, whose name is given as the successor venue name.
-
B.
hasVenueName
Indicates that an entity has a specific name used to identify the venue where an event or activity takes place.
-
C.
replacedVenue
Indicates that one venue has taken the place of another as its successor location or site.
-
D.
previousVenue
Indicates that one venue was used or occupied before another in a sequence of venues.
-
E.
formerVenueComponentOf
Indicates that a venue previously functioned as a component or part of a larger venue or venue complex, but no longer holds that status.
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 2:56 p.m.