Triple
T5764564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colchani |
E127177
|
entity |
| Predicate | economicProduct |
P31553
|
FINISHED |
| Object | table salt |
—
|
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: table salt | Statement: [Colchani, economicProduct, table salt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: economicProduct Context triple: [Colchani, economicProduct, table salt]
-
A.
economicFunction
Indicates the role or purpose an entity serves within an economic system, such as how it contributes to production, distribution, or consumption of goods and services.
-
B.
economicLink
Indicates a relationship where entities are connected through economic interactions, dependencies, or exchanges such as trade, investment, or financial flows.
-
C.
economicUse
Indicates that one entity utilizes another for economic purposes, such as production, trade, revenue generation, or cost-saving activities.
-
D.
economyIncludes
Indicates that an economy encompasses, contains, or is composed of the specified component, sector, or element.
-
E.
commercialProduct
chosen
Indicates that one entity is a product or service offered for sale or commercial use by 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0296fa3e881909359bc39892ccc18 |
completed | March 22, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69c021cc68648190bb86d049ebe80f12 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:49 p.m.