Triple
T32565094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal Stadium |
E832338
|
entity |
| Predicate | hasHomeTeamSuccessor |
P98952
|
FINISHED |
| Object | Detroit Lions |
—
|
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: Detroit Lions | Statement: [Universal Stadium, hasHomeTeamSuccessor, Detroit Lions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeTeamSuccessor Context triple: [Universal Stadium, hasHomeTeamSuccessor, Detroit Lions]
-
A.
hasSuccessorTeam
Indicates that one team is the direct successor or continuation of another team, typically following rebranding, relocation, or organizational change.
-
B.
hasNoSuccessorTeam
Indicates that an entity (typically a team) does not have any subsequent or replacement team continuing its role, identity, or lineage.
-
C.
homeTeamCurrentSuccessor
Indicates that one team is the immediate next home team in a sequence of home-team assignments or events.
-
D.
successorTeamAtBallpark
chosen
Indicates that one team is the direct successor of another as the primary tenant or home team at a particular ballpark.
-
E.
hasHomeTeamLevel
Indicates that an entity is associated with the competitive level or tier of the home team involved in a game or event.
- 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_69f34927bb308190ad94da1b11cad13c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: May 1, 2026, 1:03 a.m.