Triple
T1709452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedes-Benz Stadium |
E36943
|
entity |
| Predicate | tennantSince |
P32213
|
FINISHED |
| Object | Atlanta Falcons, 2017 |
—
|
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: Atlanta Falcons, 2017 | Statement: [Mercedes-Benz Stadium, tennantSince, Atlanta Falcons, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tennantSince Context triple: [Mercedes-Benz Stadium, tennantSince, Atlanta Falcons, 2017]
-
A.
tenantsFrom
Indicates that one or more tenants originate from, are associated with, or are derived from a specified source entity.
-
B.
laterTitleHolder
Indicates that one entity is a subsequent holder of a particular title or position previously held by another entity.
-
C.
alsoTenant
Indicates that two or more entities share the status of being tenants, typically occupying the same property or rental arrangement.
-
D.
laterHouseName
Indicates that one house or residence is known by a different name at a later time than its earlier or original name.
-
E.
hasNotablePersonWithSurname
Indicates that an entity is associated with at least one notable person who bears a specified surname.
- F. None of above. chosen
Provenance (4 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_69a88617439c819094ffb5d16a0f6307 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab7521878c8190b9e7739b8c3fc705 |
completed | March 7, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69aa61bd46d48190915500d75a9d8e94 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab752034348190a1cc20955ed24f6f |
completed | March 7, 2026, 12:45 a.m. |
Created at: March 4, 2026, 7:30 p.m.