Triple
T8771119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 71-619 |
E208462
|
entity |
| Predicate | hasElectricSystem |
P5320
|
FINISHED |
| Object | overhead line DC supply |
—
|
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: overhead line DC supply | Statement: [71-619, hasElectricSystem, overhead line DC supply]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectricSystem Context triple: [71-619, hasElectricSystem, overhead line DC supply]
-
A.
electrificationSystem
chosen
Indicates the type of electrical power system used to supply energy (typically to infrastructure or vehicles) for operation.
-
B.
electricalSystem
Indicates that one entity functions as, is part of, or is directly related to the electrical system of another entity.
-
C.
typeOfElectricity
Indicates that one entity specifies the particular kind or category of electricity associated with another entity.
-
D.
electricalPower
Indicates that one entity supplies, carries, or is associated with electrical power to or for another entity.
-
E.
hasElectrificationStatus
Indicates that an entity possesses a specified type or level of electrification (e.g., electrified, non-electrified, partially electrified).
- 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_69ca835edb4481909b4aafb616dc5eb7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f2b08f881909f3d4fab2eda1d67 |
completed | March 31, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1aff3881908be6a9cbc9f50461 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:41 p.m.