Triple
T2634195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan Railway |
E59705
|
entity |
| Predicate | laterTraction |
P28917
|
FINISHED |
| Object | electric multiple units |
—
|
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: electric multiple units | Statement: [Metropolitan Railway, laterTraction, electric multiple units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterTraction Context triple: [Metropolitan Railway, laterTraction, electric multiple units]
-
A.
successorTractionType
chosen
Indicates that one traction type directly follows or replaces another in a sequence or evolution of traction systems.
-
B.
laterTransmission
Indicates that one transmission event occurs after another in time.
-
C.
primaryTraction
Indicates that one entity serves as the main source or means of traction, pulling power, or driving force for another entity or process.
-
D.
laterPerception
Indicates that one entity’s perception, awareness, or observation of something occurs after another specified time, event, or perception.
-
E.
usedTractionType
Indicates the type of traction or drive mechanism that was employed in performing the action or operating the entity.
- 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_69ab4ac8596c8190b34997e73d9e991c |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd8def9bc8190b2e013abffc7b191 |
completed | March 7, 2026, 7:50 a.m. |
| PD | Predicate disambiguation | batch_69abd812849881908f956845a80e0205 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.