Triple
T1938862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ho Chi Minh City Metro |
E41505
|
entity |
| Predicate | Line 1 length |
P266
|
FINISHED |
| Object | approximately 19.7 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 19.7 km | Statement: [Ho Chi Minh City Metro, Line 1 length, approximately 19.7 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Line 1 length Context triple: [Ho Chi Minh City Metro, Line 1 length, approximately 19.7 km]
-
A.
hasNumberOfLines
Indicates the relationship that specifies how many lines are associated with a given entity.
-
B.
mainStraightLengthM
Indicates the length, measured in meters, of the main straight segment (typically of a track, road, or similar linear feature).
-
C.
length
chosen
Indicates a measurement relationship where a value specifies how long something is from one end to the other.
-
D.
mainStraightLengthKm
Indicates the length, measured in kilometers, of the primary straight segment associated with the entity.
-
E.
lineElement
Indicates a relationship where something functions as, or is identified as, an element or segment of a line within a larger linear structure or representation.
- 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb2c8be648190836580cec77a143f |
completed | March 7, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69abaff07cf88190b4883c5f17f90abd |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.