Triple
T24094690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlanta Braves television broadcasts |
E596882
|
entity |
| Predicate | regionalMarket |
P12320
|
FINISHED |
| Object | Southeastern United States |
—
|
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: Southeastern United States | Statement: [Atlanta Braves television broadcasts, regionalMarket, Southeastern United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionalMarket Context triple: [Atlanta Braves television broadcasts, regionalMarket, Southeastern United States]
-
A.
marketRegion
chosen
Indicates the geographic or demographic area in which a product, service, or entity is actively marketed or targeted.
-
B.
regionalType
Indicates the classification of a region according to its designated type or category within a broader geographic or administrative system.
-
C.
isRegional
Indicates that something pertains to, is characteristic of, or is limited to a specific geographic region or area.
-
D.
catalogRegion
Indicates the geographic or organizational region associated with a given catalog or catalog entry.
-
E.
campaignRegion
Indicates the geographic area or territory in which a campaign is conducted or targeted.
- 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_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. |
Created at: April 17, 2026, 10:58 p.m.