Triple
T97662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IRT Division |
E1967
|
entity |
| Predicate | usesPowerSupply |
P1870
|
FINISHED |
| Object | 600 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: 600 V DC third rail | Statement: [IRT Division, usesPowerSupply, 600 V DC third rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPowerSupply Context triple: [IRT Division, usesPowerSupply, 600 V DC third rail]
-
A.
usesElectricityStandard
Indicates that one entity operates according to, or is compatible with, the electricity supply standard defined or used by another entity.
-
B.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
C.
usesElectricityVoltage
chosen
Indicates that one entity operates using or is characterized by a specified level of electrical voltage supplied by another entity or source.
-
D.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
E.
usesEquipment
Indicates that an entity employs or operates a particular piece of equipment to perform an action or fulfill a function.
- 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a24feef1b08190bb9525f71cce053e |
completed | Feb. 28, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69a24ebe7b1c8190a6bfbf31dc7c7f07 |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.