Triple
T5073466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kobuk |
E114335
|
entity |
| Predicate | hasElectricPower |
P8164
|
FINISHED |
| Object | local diesel 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: local diesel generation | Statement: [Kobuk, hasElectricPower, local diesel generation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectricPower Context triple: [Kobuk, hasElectricPower, local diesel generation]
-
A.
electricalPower
Indicates that one entity supplies, carries, or is associated with electrical power to or for another entity.
-
B.
hasElectricCharge
Indicates that an entity possesses a nonzero electric charge as a physical property.
-
C.
hasElectrificationStatus
Indicates that an entity possesses a specified type or level of electrification (e.g., electrified, non-electrified, partially electrified).
-
D.
hasPowerSource
chosen
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
E.
electrificationSystem
Indicates the type of electrical power system used to supply energy (typically to infrastructure or vehicles) for operation.
- 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_69bd443cf28c8190ad371d603563dbdd |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74cfa4348190bc50590117a6bcf9 |
completed | March 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.