Triple
T1373597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trenton Line |
E30168
|
entity |
| Predicate | electrifiedBy |
P5320
|
FINISHED |
| Object | 25 kV AC (Northeast Corridor standard) |
—
|
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: 25 kV AC (Northeast Corridor standard) | Statement: [Trenton Line, electrifiedBy, 25 kV AC (Northeast Corridor standard)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electrifiedBy Context triple: [Trenton Line, electrifiedBy, 25 kV AC (Northeast Corridor standard)]
-
A.
electrificationSystem
chosen
Indicates the type of electrical power system used to supply energy (typically to infrastructure or vehicles) for operation.
-
B.
electrification
Indicates the process or state of providing electrical power or converting something to operate using electricity.
-
C.
hasElectricCharge
Indicates that an entity possesses a nonzero electric charge as a physical property.
-
D.
electrificationCompleted
Indicates that the process of providing electrical power infrastructure to the relevant entity or area has been fully completed.
-
E.
electrificationEnd
Indicates the point in time or event at which an electrification process or electrified state comes to an end.
- 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_69a498f912008190a376a98b207b2071 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c2f660888190bc9240e0dc4f0aa3 |
completed | March 1, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69a4befcabdc8190a9f05d002603f81c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:57 p.m.