Triple
T15795844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gawler railway line |
E382974
|
entity |
| Predicate | formerTraction |
P111366
|
FINISHED |
| Object | diesel 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: diesel multiple units | Statement: [Gawler railway line, formerTraction, diesel multiple units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerTraction Context triple: [Gawler railway line, formerTraction, diesel multiple units]
-
A.
previousTractionType
chosen
Indicates the type of traction or traction method that was used previously before the current one.
-
B.
usedTractionType
Indicates the type of traction or drive mechanism that was employed in performing the action or operating the entity.
-
C.
secondaryTraction
Indicates a supporting or additional influence, pull, or driving force that complements a primary source of traction or momentum in a relationship or process.
-
D.
successorTractionType
Indicates that one traction type directly follows or replaces another in a sequence or evolution of traction systems.
-
E.
formerTransport
Indicates that an entity previously served as a means of transportation for another entity but no longer does so.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4dc887081909d682ae153f06d97 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:48 a.m.