Triple
T787523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airport Line |
E16837
|
entity |
| Predicate | electrificationVoltage |
P5320
|
FINISHED |
| Object | 12 kV AC |
—
|
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: 12 kV AC | Statement: [Airport Line, electrificationVoltage, 12 kV AC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electrificationVoltage Context triple: [Airport Line, electrificationVoltage, 12 kV AC]
-
A.
usesElectricityVoltage
Indicates that one entity operates using or is characterized by a specified level of electrical voltage supplied by another entity or source.
-
B.
electrificationSystem
chosen
Indicates the type of electrical power system used to supply energy (typically to infrastructure or vehicles) for operation.
-
C.
electrification
Indicates the process or state of providing electrical power or converting something to operate using electricity.
-
D.
electrificationUsedBetween
Indicates that an electrification system or method is applied or present along the segment or connection between two entities.
-
E.
usesElectricFrequency
Indicates that one entity operates or functions by relying on a specified electric frequency provided by another entity or 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a78171908190a38a70274bfbebf9 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a50ef72c819084ffe9f31dbd0262 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:38 p.m.