Triple
T24062282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brayton Point Power Station |
E595985
|
entity |
| Predicate | fuelTransport |
P154706
|
FINISHED |
| Object | coal delivered by ship |
—
|
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 delivered by ship | Statement: [Brayton Point Power Station, fuelTransport, coal delivered by ship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelTransport Context triple: [Brayton Point Power Station, fuelTransport, coal delivered by ship]
-
A.
fuelRole
Indicates that one entity serves as the fuel or energy source used or consumed by another entity in a process or operation.
-
B.
fuelForm
Indicates the physical or chemical form in which a fuel exists or is supplied (e.g., liquid, gas, solid).
-
C.
fuelCharacteristic
Indicates a relationship where a fuel is associated with one of its defining properties or qualities, such as composition, performance, or behavior.
-
D.
fuelConsumption
Indicates the amount of fuel used by an entity (such as a vehicle or device) over a specified distance, time, or operation.
-
E.
typicalFuel
Indicates the kind of fuel that is normally or most commonly used by an entity (such as a device, vehicle, or system).
- 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_69e288c25c008190850cf447940ab181 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1da5735cc81908f22e2a20b4c1c90 |
completed | April 29, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 10:38 p.m.