Triple
T18608722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rugeley power station A |
E454826
|
entity |
| Predicate | fuelHandling |
P8247
|
FINISHED |
| Object | coal conveyor systems |
—
|
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 conveyor systems | Statement: [Rugeley power station A, fuelHandling, coal conveyor systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelHandling Context triple: [Rugeley power station A, fuelHandling, coal conveyor systems]
-
A.
fuelLocation
Indicates the place or source where fuel is stored, supplied, or located for use.
-
B.
fuelSystem
chosen
Indicates a relationship where one entity serves as the fuel system (or part of it) that supplies, stores, or manages fuel for the operation of another entity.
-
C.
fuelForm
Indicates the physical or chemical form in which a fuel exists or is supplied (e.g., liquid, gas, solid).
-
D.
fuelControl
Indicates a relationship where one entity regulates, manages, or influences the supply or use of fuel for another entity or system.
-
E.
fuelFraction
Indicates the proportion of an object's total mass or capacity that consists of fuel.
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54cff3be8819080ab20045bd18a4d |
completed | April 19, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:45 a.m.