Triple
T33922022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reunification Express line |
E869639
|
entity |
| Predicate | primaryRailCorridorOf |
P109925
|
FINISHED |
| Object | Vietnam |
E4138
|
NE 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: Vietnam | Statement: [Reunification Express line, primaryRailCorridorOf, Vietnam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRailCorridorOf Context triple: [Reunification Express line, primaryRailCorridorOf, Vietnam]
-
A.
primaryCorridorServed
Indicates that a corridor is the main route or pathway served by a given service, facility, or entity.
-
B.
regionRailCorridor
Indicates a rail transport corridor that runs within or through a specified region.
-
C.
railCorridorType
Indicates the specific classification or type of a rail corridor associated with the subject (e.g., mainline, branch line, high-speed, freight, etc.).
-
D.
majorTransportCorridor
Indicates that a route or pathway functions as a primary, high-capacity channel for transporting people or goods between significant locations.
-
E.
primaryRailLinkFor
chosen
Indicates that one entity serves as the main or principal rail connection or route for another entity.
- F. None of above.
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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3682426254819091078d7566595e02 |
completed | June 20, 2026, 12:06 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:49 a.m.