Triple
T8698151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otavalo Canton |
E206452
|
entity |
| Predicate | marketSpecialty |
P43327
|
FINISHED |
| Object | textiles |
—
|
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: textiles | Statement: [Otavalo Canton, marketSpecialty, textiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketSpecialty Context triple: [Otavalo Canton, marketSpecialty, textiles]
-
A.
marketSpecialization
chosen
Indicates a relationship where an entity focuses its activities, products, or services on serving a specific segment or niche of a broader market.
-
B.
marketsThrough
Indicates that one entity promotes, sells, or distributes its products or services by using another entity as a marketing or sales channel.
-
C.
marketTrait
Indicates that an entity possesses a particular characteristic, behavior, or attribute relevant to how it functions or is perceived in a market context.
-
D.
marketsIn
Indicates that one entity promotes, sells, or offers another entity’s products or services within a particular market or geographic area.
-
E.
marketType
Indicates the classification or category of market in which an entity operates or a transaction occurs (e.g., retail, wholesale, online).
- 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_69ca83555b6c8190abe930dd397e863b |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc58af50408190a3b81100a759795e |
completed | March 31, 2026, 11:28 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:34 p.m.