Triple
T24094708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlanta Braves television broadcasts |
E596882
|
entity |
| Predicate | homeVenueCovered |
P155056
|
FINISHED |
| Object | Truist Park |
—
|
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: Truist Park | Statement: [Atlanta Braves television broadcasts, homeVenueCovered, Truist Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeVenueCovered Context triple: [Atlanta Braves television broadcasts, homeVenueCovered, Truist Park]
-
A.
homeVenueIncludes
Indicates that a specified venue is part of, contained within, or used as a home location by another entity.
-
B.
homeVenueOwned
Indicates that the specified home venue is legally owned or possessed by the associated entity.
-
C.
homeMeetsVenue
Indicates that a home team plays its scheduled match at a specified venue.
-
D.
homeVenueFocus
Indicates a primary or central emphasis on a particular venue as the main location associated with an entity’s activities or presence.
-
E.
home venue type
Indicates the kind or category of place that serves as the primary location where an entity regularly hosts its events or activities.
- 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_69e288c548048190a5c1018da1166a21 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dd2332b48190a711b2a0a304f3c2 |
completed | April 29, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17b58012c81909106b332db399023 |
completed | April 29, 2026, 3:30 a.m. |
Created at: April 17, 2026, 10:58 p.m.