Triple
T2673020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pontiac, Michigan |
E56390
|
entity |
| Predicate | hasSportsVenueHistory |
P41607
|
FINISHED |
| Object | former NFL venue Pontiac Silverdome |
—
|
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: former NFL venue Pontiac Silverdome | Statement: [Pontiac, Michigan, hasSportsVenueHistory, former NFL venue Pontiac Silverdome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSportsVenueHistory Context triple: [Pontiac, Michigan, hasSportsVenueHistory, former NFL venue Pontiac Silverdome]
-
A.
hasProfessionalSportsVenue
Indicates that one entity possesses or hosts a venue specifically used for professional sports events.
-
B.
hasSportsVenueType
Indicates that a sports venue is classified as being of a specific type or category (e.g., stadium, arena, court).
-
C.
hasMajorVenue
Indicates that an entity is associated with a primary or principal venue where its main activities or events take place.
-
D.
hasSportsTeamVenueFor
Indicates that a venue serves as the home or hosting location for a particular sports team.
-
E.
sportsVenueFor
Indicates that a venue is used as the location or facility where a particular sport or sporting event takes place.
- 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_69ab4a4b13fc81909dfdb3f23da46832 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9b08b1c8190824342fc63e555d2 |
completed | March 7, 2026, 7:54 a.m. |
| PD | Predicate disambiguation | batch_69abd8190ad481908f3e14ac84d0940a |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd8f98c348190a68064c565589459 |
completed | March 7, 2026, 7:51 a.m. |
Created at: March 6, 2026, 9:54 p.m.