Triple
T32053787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macon television market |
E818560
|
entity |
| Predicate | primaryCityOfMarket |
P3940
|
FINISHED |
| Object | Macon, Georgia |
E1639923
|
NE 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: Macon, Georgia | Statement: [Macon television market, primaryCityOfMarket, Macon, Georgia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCityOfMarket Context triple: [Macon television market, primaryCityOfMarket, Macon, Georgia]
-
A.
primaryCity
chosen
Indicates that one city serves as the main or most important city associated with a given region, entity, or context.
-
B.
principalCityOf
Indicates that a city serves as the main or most important city (often administrative, economic, or cultural center) of a specified region or area.
-
C.
primaryShareTradingCity
Indicates the city where an entity’s shares are primarily traded on a stock exchange.
-
D.
marketCity
Indicates that a city serves as a primary marketplace or commercial center for a given region or entity.
-
E.
primaryLocationCity
Indicates the city that serves as the main or primary location associated with the subject.
- F. None of above.
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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34b1435b748190896af3d2104e629c |
completed | June 19, 2026, 3:02 a.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:21 a.m.