Triple
T27915369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GE ES44DC |
E706053
|
entity |
| Predicate | tractionCurrentType |
P58828
|
FINISHED |
| Object | direct current |
—
|
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: direct current | Statement: [GE ES44DC, tractionCurrentType, direct current]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tractionCurrentType Context triple: [GE ES44DC, tractionCurrentType, direct current]
-
A.
tractionCurrentCollection
Indicates the relationship between a traction system and the specific collection of electric current (e.g., via pantograph or third rail) it is using or associated with.
-
B.
tractionType
Indicates the type or method of traction applied or used in relation to an entity or system.
-
C.
currentTractionType
chosen
Indicates the type or mode of traction currently being applied or in use in a given context.
-
D.
associatedCurrent
Indicates a relationship where a particular current is linked or connected to another entity as its relevant or corresponding current.
-
E.
conventionalCurrent
Indicates the direction in which positive electric charge is considered to flow in a circuit, from higher to lower electric potential, regardless of the actual motion of electrons.
- 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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 6:53 p.m.