Triple
T38677955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DiscoVision |
E943808
|
entity |
| Predicate | firstMarketedRegion |
P12320
|
FINISHED |
| Object | Atlanta, Georgia test market |
—
|
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: Atlanta, Georgia test market | Statement: [DiscoVision, firstMarketedRegion, Atlanta, Georgia test market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMarketedRegion Context triple: [DiscoVision, firstMarketedRegion, Atlanta, Georgia test market]
-
A.
countryOfFirstMarketing
Indicates the country where a product was first introduced or made available on the market.
-
B.
marketRegion
chosen
Indicates the geographic or demographic area in which a product, service, or entity is actively marketed or targeted.
-
C.
launchedInCountry
Indicates that an entity (such as a product, service, or mission) was officially initiated, introduced, or started within a specified country.
-
D.
firstAiredInMarket
Indicates the date or time when a piece of content was initially broadcast or released in a specific market or region.
-
E.
developedInRegion
Indicates that something was created, produced, or brought into existence within a specified geographic region.
- 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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:33 p.m.