Triple
T16853580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National |
E409731
|
entity |
| Predicate | geographicBrandUsage |
P55272
|
FINISHED |
| Object | primarily Asia |
—
|
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: primarily Asia | Statement: [National, geographicBrandUsage, primarily Asia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicBrandUsage Context triple: [National, geographicBrandUsage, primarily Asia]
-
A.
brandUsage
Indicates that one entity uses, features, or is associated with another entity’s brand in its products, services, or communications.
-
B.
brandUsedInCountry
Indicates that a particular brand is used or present within a specified country.
-
C.
usedInCountryOrRegion
Indicates that something (such as an item, concept, or practice) is utilized or applied within a specified country or region.
-
D.
countryOrRegionOfPrevalence
chosen
Indicates the country or geographic region where something (such as a condition, practice, or phenomenon) is most commonly found or occurs most frequently.
-
E.
distributedBrand
Indicates that one entity serves as a distributor or reseller for the brand of another entity.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b37bbb80819086d844a313625cad |
completed | April 18, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.