Triple
T19715203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rungata |
E473457
|
entity |
| Predicate | hasElectricitySource |
P8164
|
FINISHED |
| Object | 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: diesel generators | Statement: [Rungata, hasElectricitySource, diesel generators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectricitySource Context triple: [Rungata, hasElectricitySource, diesel generators]
-
A.
isMajorSourceOfElectricityFor
Indicates that one entity provides the primary or dominant share of electrical power used by another entity.
-
B.
hasPowerSource
chosen
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
C.
usesElectricityFor
Indicates that one entity relies on or employs electricity as the power source to operate, perform a function, or carry out an activity for another entity or purpose.
-
D.
typeOfElectricity
Indicates that one entity specifies the particular kind or category of electricity associated with another entity.
-
E.
electrificationServedBy
Indicates that the electrification of a system, area, or infrastructure is provided, supported, or enabled by a specified source, service, or 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6440cb47c81908124dfbd6f781d23 |
completed | April 20, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.