Triple
T9294023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SRT high-speed rail |
E223592
|
entity |
| Predicate | railwayTrafficSide |
P6244
|
FINISHED |
| Object | left |
—
|
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: left | Statement: [SRT high-speed rail, railwayTrafficSide, left]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayTrafficSide Context triple: [SRT high-speed rail, railwayTrafficSide, left]
-
A.
railNetworkSide
chosen
Indicates on which side of a rail network (e.g., left or right relative to a reference direction) an entity is located or associated.
-
B.
railwayTraffic
Indicates the presence, flow, or management of train movements along railway lines between locations.
-
C.
coordinatesRailTrafficWith
Indicates that one entity organizes and synchronizes rail operations or movements with another entity to ensure coordinated train traffic.
-
D.
railTracks
Indicates that one entity consists of, includes, or is associated with rail tracks used for guiding trains or rail vehicles.
-
E.
railInterface
Indicates a connection or interaction between entities via a rail-based system or interface.
- 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd089a2ed0819086b2e4219ff2453e |
completed | April 1, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_69cc7a5aeb748190afb89c6bbd2a6d6f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:35 p.m.