Triple
T32804355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Giants vs. Philadelphia Eagles game, December 2010 |
E838979
|
entity |
| Predicate | laterStadiumName |
P26494
|
FINISHED |
| Object | MetLife 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: MetLife Stadium | Statement: [New York Giants vs. Philadelphia Eagles game, December 2010, laterStadiumName, MetLife Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterStadiumName Context triple: [New York Giants vs. Philadelphia Eagles game, December 2010, laterStadiumName, MetLife Stadium]
-
A.
mainStadiumLaterName
chosen
Indicates that the main stadium associated with an entity was later renamed to the specified new name.
-
B.
lastStadium
Indicates that one stadium is the final or most recent stadium associated with a particular entity, such as a team, event, or player.
-
C.
stadiumAlsoKnownAs
Indicates that a stadium has an alternative name or alias by which it is also known.
-
D.
stadiumOfficialName
Indicates the formal, legally recognized name assigned to a stadium.
-
E.
neighbouringStadium
Indicates that one stadium is located adjacent to or very close to another stadium.
- 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_69f3493d35208190b4351b4e85f2fa16 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffacdf9f5c8190baef0245edfe87fc |
completed | May 9, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69ffac5e86e08190a1e6da0840a237ad |
completed | May 9, 2026, 9:51 p.m. |
Created at: May 1, 2026, 1:15 a.m.