Triple
T5774873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WMATA 3000-series railcar |
E127414
|
entity |
| Predicate | designedForVoltage |
P1870
|
FINISHED |
| Object | 750 V DC third rail |
—
|
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: 750 V DC third rail | Statement: [WMATA 3000-series railcar, designedForVoltage, 750 V DC third rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForVoltage Context triple: [WMATA 3000-series railcar, designedForVoltage, 750 V DC third rail]
-
A.
usesElectricityVoltage
chosen
Indicates that one entity operates using or is characterized by a specified level of electrical voltage supplied by another entity or source.
-
B.
supportsMaximumVoltage
Indicates that an entity is capable of safely operating at or up to a specified maximum voltage level.
-
C.
supplyVoltageType
Indicates the type or category of supply voltage associated with or required by an entity.
-
D.
typicalVoltagePerCell
Indicates the standard or commonly expected voltage value associated with each individual cell in a multi-cell system or device.
-
E.
maxVoltage
Indicates the maximum electrical potential (voltage) that an entity can safely or normally handle, provide, or operate at.
- 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_69c008361fa88190aefa4dc41b051e7f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021d0c6088190ba670ddcdbf5ca3e |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:50 p.m.