Triple
T28281885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matsuura Railway |
E713170
|
entity |
| Predicate | rollingStockPower |
P70927
|
FINISHED |
| Object | diesel |
—
|
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 | Statement: [Matsuura Railway, rollingStockPower, diesel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rollingStockPower Context triple: [Matsuura Railway, rollingStockPower, diesel]
-
A.
rollingStockPowerSupply
chosen
Indicates that one rolling stock entity provides or is associated with a specific power supply used to operate or support another entity.
-
B.
rollingStockType
Indicates the specific category or type of railway rolling stock associated with an entity (e.g., locomotive, passenger car, freight wagon).
-
C.
locomotiveWeight
Indicates the weight or mass of a locomotive in the relationship.
-
D.
rollingStockLength
Indicates the length measurement of a piece of rolling stock in a rail or transit system.
-
E.
rollingStockFamily
Indicates a relationship where a piece of rolling stock belongs to, or is classified under, a particular family or series of related rolling stock designs.
- 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_69efb52275788190ae5181ccebef18ce |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f64451040881909310d73fc91bccfb |
completed | May 2, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:23 p.m.