Triple
T6660237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinxton |
E151455
|
entity |
| Predicate | historicEconomicActivity |
P10778
|
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: [Pinxton, historicEconomicActivity, coal mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicEconomicActivity Context triple: [Pinxton, historicEconomicActivity, coal mining]
-
A.
historicalEconomicBase
chosen
Indicates the primary type of economic activity or production that historically underpinned or sustained an entity’s economy.
-
B.
historicActivity
Indicates that an entity engaged in an activity or event of historical significance in the past.
-
C.
historicalPeriodOfMajorActivity
Indicates the historical period during which an entity carried out its most significant or influential activities.
-
D.
hasTraditionalEconomyActivity
Indicates that an entity engages in or is associated with economic activities based on traditional practices, customs, or subsistence methods.
-
E.
historicalCategory
Indicates that an entity is classified within a particular historical grouping, period, or type based on its time-related characteristics or context.
- 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_69c687f5fac48190a09e4838d9c6b45d |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9d53848190ac75523c157249c6 |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad071b0081909b96dd4b93414bd1 |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:02 p.m.