Triple
T34603501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Choppington |
E888529
|
entity |
| Predicate | hasFormerEconomicActivity |
P19843
|
FINISHED |
| Object | coal mining |
—
|
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: coal mining | Statement: [Choppington, hasFormerEconomicActivity, coal mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerEconomicActivity Context triple: [Choppington, hasFormerEconomicActivity, coal mining]
-
A.
hasEconomicActivity
Indicates that an entity engages in, supports, or is associated with a specific type of economic activity or business operation.
-
B.
formerEconomicActivity
chosen
Indicates that an entity previously engaged in a specified economic activity but no longer does so.
-
C.
hasFormerBusiness
Indicates that an entity previously had a business relationship or partnership with another entity, but that relationship is no longer current.
-
D.
hasPastOccupation
Indicates that an entity previously held a particular job, role, or occupation in the past.
-
E.
hasEntrepreneurialActivity
Indicates that an entity engages in or is associated with starting, managing, or operating business or venture-related activities.
- 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_69f349d489d48190ba30e7d97c6f5ef9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: May 1, 2026, 2:03 a.m.