Triple
T22476145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First National Bank Field |
E555633
|
entity |
| Predicate | isProfessionalSportsVenue |
P148349
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [First National Bank Field, isProfessionalSportsVenue, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isProfessionalSportsVenue Context triple: [First National Bank Field, isProfessionalSportsVenue, true]
-
A.
hasProfessionalSportsVenue
Indicates that one entity possesses or hosts a venue specifically used for professional sports events.
-
B.
isPartOfSportsVenue
Indicates that one entity is a component, section, or area contained within a larger sports venue.
-
C.
sportsVenueFor
Indicates that a venue is used as the location or facility where a particular sport or sporting event takes place.
-
D.
hasSportsVenueType
Indicates that a sports venue is classified as being of a specific type or category (e.g., stadium, arena, court).
-
E.
ownsSportsVenue
Indicates that one entity possesses legal ownership or controlling property rights over a sports venue used for athletic or sporting events.
- 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_69e11e52c2048190952dc5df209b9bed |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15be48cec8190baff90f8566a85d0 |
completed | April 29, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:49 p.m.