Triple
T5047961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinki Sharyo |
E113712
|
entity |
| Predicate | transportSegment |
P60863
|
FINISHED |
| Object | passenger 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: passenger rail | Statement: [Kinki Sharyo, transportSegment, passenger rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportSegment Context triple: [Kinki Sharyo, transportSegment, passenger rail]
-
A.
transportCorridor
Indicates a route or pathway used to move people, goods, or resources between locations.
-
B.
crewTransportSegment
Indicates a segment of a journey during which crew members are transported from one location to another.
-
C.
transportHubType
Indicates the specific category or kind of transport hub associated with an entity (e.g., airport, train station, bus terminal).
-
D.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
E.
transportationJunctionFor
Indicates a location that serves as a connecting point where multiple transportation routes or modes meet, intersect, or transfer.
- F. None of above. chosen
Provenance (4 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7401419081909ba62b9c27f770c4 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd715479f08190933604aebd34414f |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd73089f548190834103366e24ab40 |
completed | March 20, 2026, 4:17 p.m. |
Created at: March 20, 2026, 1:37 p.m.