Triple
T2576230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BAT |
E57781
|
entity |
| Predicate | marketReach |
P39897
|
FINISHED |
| Object | worldwide |
—
|
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: worldwide | Statement: [BAT, marketReach, worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketReach Context triple: [BAT, marketReach, worldwide]
-
A.
mediaMarket
Indicates a relationship where a media outlet or content provider serves, targets, or operates within a particular geographic or demographic market.
-
B.
marketUse
Indicates that something is used, applied, or exploited within a market or commercial context.
-
C.
marketingAs
Indicates that one entity is being presented, promoted, or branded to others as if it were another specified entity, role, or category.
-
D.
targetMarket
Indicates the group of consumers or organizations that a product, service, or campaign is specifically intended and designed to reach.
-
E.
coreMarket
Indicates that an entity serves as the primary or most important market for another entity’s products, services, 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_69ab4a51410081908501dcf8bad9adc4 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3a606e481909bcea46de468bb99 |
completed | March 7, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69abd0ce4dcc8190b17a65abf9bd1bb0 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd251b48c8190862c7b39ea1bf8ea |
completed | March 7, 2026, 7:22 a.m. |
Created at: March 6, 2026, 9:49 p.m.