Triple
T16837121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhundong coalfield |
E409311
|
entity |
| Predicate | energyBaseType |
P125049
|
FINISHED |
| Object | integrated coal-power-chemical base |
—
|
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: integrated coal-power-chemical base | Statement: [Zhundong coalfield, energyBaseType, integrated coal-power-chemical base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyBaseType Context triple: [Zhundong coalfield, energyBaseType, integrated coal-power-chemical base]
-
A.
energyType
Indicates the kind or category of energy associated with an entity or process.
-
B.
energyRegime
Indicates the specific range or mode of energy conditions under which a process, interaction, or system operates or is characterized.
-
C.
energyContribution
Indicates the amount or role of energy that one entity provides or contributes to another entity, process, or system.
-
D.
energyHub
Indicates a central entity that collects, manages, and distributes energy or power among connected entities or systems.
-
E.
energyContext
Indicates the situational or environmental conditions under which energy is produced, used, transferred, or transformed in relation to the entities involved.
- F. None of above. chosen
Provenance (4 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b34e080c8190bf7a236205b41db2 |
completed | April 18, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e34fb7c8c8819086975b7955b7d8ef |
completed | April 18, 2026, 9:32 a.m. |
Created at: April 10, 2026, 5:23 a.m.