Triple
T37815374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sygun Copper Mine area |
E942758
|
entity |
| Predicate | primaryEconomicRolePast |
P19843
|
FINISHED |
| Object | metal ore extraction |
—
|
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: metal ore extraction | Statement: [Sygun Copper Mine area, primaryEconomicRolePast, metal ore extraction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryEconomicRolePast Context triple: [Sygun Copper Mine area, primaryEconomicRolePast, metal ore extraction]
-
A.
economicRolePast
Indicates that an entity previously held a specific economic function, position, or role in the past.
-
B.
formerEconomicActivity
chosen
Indicates that an entity previously engaged in a specified economic activity but no longer does so.
-
C.
earlierOccupation
Indicates that one occupation held by an entity occurred before another occupation in that entity’s work history.
-
D.
workedPrimarilyIn
Indicates that an entity carried out the majority of its work, activity, or career within a particular field, location, or context.
-
E.
workedPrimarilyOn
Indicates that an entity devoted the majority of its work, effort, or activity to a particular project, field, or subject.
- 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_69f76ee987588190906506e759be5db3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.