Triple
T28214561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TUDMB |
E711274
|
entity |
| Predicate | performsAtVenue |
P96050
|
FINISHED |
| Object | Lincoln Financial Field |
—
|
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: Lincoln Financial Field | Statement: [TUDMB, performsAtVenue, Lincoln Financial Field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performsAtVenue Context triple: [TUDMB, performsAtVenue, Lincoln Financial Field]
-
A.
performedAtVenue
chosen
Indicates that an event or performance took place at a specific venue or location.
-
B.
hasVenueFor
Indicates that one entity provides or serves as the location or setting where an event, activity, or function takes place for another entity.
-
C.
connectsToEventVenue
Indicates that one entity serves as a link or route providing access or connection to an event venue.
-
D.
hasVenueIn
Indicates that an event, activity, or occurrence takes place at a specific venue located within a particular geographic area or location.
-
E.
laterPerformanceVenue
Indicates that a performance or event took place at this venue at a later time than another referenced performance or venue.
- 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 27, 2026, 10:41 p.m.