Triple
T18029953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evenki culture |
E431358
|
entity |
| Predicate | coreEconomicActivity |
P16022
|
FINISHED |
| Object | reindeer herding |
—
|
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: reindeer herding | Statement: [Evenki culture, coreEconomicActivity, reindeer herding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreEconomicActivity Context triple: [Evenki culture, coreEconomicActivity, reindeer herding]
-
A.
economicClassification
Indicates how an entity is categorized based on its economic characteristics, status, or role within an economic system.
-
B.
economicSectorDominant
Indicates that one economic sector holds a leading or controlling position relative to others in terms of influence, output, or importance.
-
C.
economicSectorSourceOfWealth
chosen
Indicates that a particular economic sector is the primary source from which an entity derives its wealth or income.
-
D.
regionalEconomyActivity
Indicates the type or level of economic activity occurring within a specific geographic region.
-
E.
economicExtensionOf
Indicates that one entity’s economy is heavily dependent on, controlled by, or functions as an outgrowth of another entity’s economic system.
- 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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4be347f6c8190b324fe74b7dc1764 |
completed | April 19, 2026, 11:36 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.