Triple
T27321501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuntutuliak, Alaska |
E689508
|
entity |
| Predicate | hasElectricPowerSource |
P58530
|
FINISHED |
| Object | local diesel generators |
—
|
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 generators | Statement: [Tuntutuliak, Alaska, hasElectricPowerSource, local diesel generators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectricPowerSource Context triple: [Tuntutuliak, Alaska, hasElectricPowerSource, local diesel generators]
-
A.
hasPowerSource
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
B.
hasElectricMotor
Indicates that an entity is equipped with, contains, or uses an electric motor as part of its operation or structure.
-
C.
isElectrically
Indicates that one entity has an electrical property, connection, or interaction in relation to another entity.
-
D.
hasElectricCharge
Indicates that an entity possesses a nonzero electric charge as a physical property.
-
E.
electricalPower
chosen
Indicates that one entity supplies, carries, or is associated with electrical power to or for another entity.
- 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_69ef355c53a08190a8a92e355a7ce115 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 11:33 a.m.