Triple
T36164534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dover Colliery |
E1045962
|
entity |
| Predicate | hasOutputUse |
P92
|
FINISHED |
| Object | electricity generation |
—
|
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: electricity generation | Statement: [Dover Colliery, hasOutputUse, electricity generation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutputUse Context triple: [Dover Colliery, hasOutputUse, electricity generation]
-
A.
hasOutputUser
Indicates that an entity produces, returns, or is associated with a specific user as its output.
-
B.
hasOutputType
chosen
Indicates that an entity produces, returns, or yields a result of a specified type.
-
C.
hasOutputFeature
Indicates that an entity produces, exposes, or is associated with a particular output characteristic or feature as a result of its operation or behavior.
-
D.
outputUsedBy
Indicates that a particular output produced by one entity is consumed, referenced, or otherwise utilized by another entity.
-
E.
hasLiveUse
Indicates that something is currently being used or actively in operation in a live, real-world 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.