Triple
T8369285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vietnam Railways network |
E197412
|
entity |
| Predicate | mainRouteLength_NorthSouthRailway |
P68820
|
FINISHED |
| Object | approximately 1726 km |
—
|
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: approximately 1726 km | Statement: [Vietnam Railways network, mainRouteLength_NorthSouthRailway, approximately 1726 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainRouteLength_NorthSouthRailway Context triple: [Vietnam Railways network, mainRouteLength_NorthSouthRailway, approximately 1726 km]
-
A.
railwayLineLength
Indicates the total measured length of a railway line.
-
B.
northSouthRoutes
Indicates that there are routes or connections running in a generally north–south direction between the related entities.
-
C.
totalRouteLength
chosen
Indicates the overall distance or length of an entire route when all its segments are combined.
-
D.
railwayLine
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
E.
mainStraightLengthKm
Indicates the length, measured in kilometers, of the primary straight segment associated with 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_69ca82f56730819080cec5d991c76f4c |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb808f7c0481909fef5834cb6e7a3e |
completed | March 31, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69cb70cd04b08190ab5f72afd22a7967 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:01 p.m.