Triple
T27700132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Land Shark Stadium |
E698403
|
entity |
| Predicate | wasReplacedByName |
P23044
|
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, wasReplacedByName, Sun Life Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasReplacedByName Context triple: [Land Shark Stadium, wasReplacedByName, Sun Life Stadium]
-
A.
hasReplaced
Indicates that one entity has taken the place or function of another entity, superseding it in a given context.
-
B.
replacementName
chosen
Indicates that one entity serves as a substitute or successor name for another entity, effectively replacing the original designation.
-
C.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
D.
replacedBecause
Indicates that one entity has been substituted for another specifically due to a particular reason or cause.
-
E.
createdToReplace
Indicates that one entity was intentionally created for the purpose of taking over the role, function, or position of another entity.
- 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_69f635a29ff08190bfd246ccaf0ddb4e |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:56 p.m.