Triple
T4432943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Notre Dame Stadium |
E95376
|
entity |
| Predicate | replacedSurfaceWithNaturalGrass |
P55974
|
FINISHED |
| Object | 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: 2017 | Statement: [Notre Dame Stadium, replacedSurfaceWithNaturalGrass, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedSurfaceWithNaturalGrass Context triple: [Notre Dame Stadium, replacedSurfaceWithNaturalGrass, 2017]
-
A.
homeFieldSurface
Indicates the type of playing surface used at a team's home field or stadium.
-
B.
coversGrounds
Indicates that one entity extends over, occupies, or lies across the surface area of another entity (typically land or grounds).
-
C.
replacedByAsMainFootballVenue
Indicates that one football venue has been superseded by another as the primary location for hosting football events.
-
D.
homeGroundType
Indicates the type or category of venue that serves as an entity’s designated home ground.
-
E.
parkSectionReplaced
Indicates that one section of a park has been replaced by another section, typically as part of an update, renovation, or redesign.
- 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_69b3453c2a0c8190926b574c90766db9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3556cd83881908547aa311c4f17fa |
completed | March 13, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69b34f6078cc8190831b89f404198cc5 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3505a87b4819083fbbd58870e520b |
completed | March 12, 2026, 11:46 p.m. |
Created at: March 12, 2026, 11:31 p.m.