Triple
T33922050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reunification Express line |
E869639
|
entity |
| Predicate | notableScenicSection |
P193015
|
FINISHED |
| Object | Hai Van Pass area |
E425581
|
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: Hai Van Pass area | Statement: [Reunification Express line, notableScenicSection, Hai Van Pass area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableScenicSection Context triple: [Reunification Express line, notableScenicSection, Hai Van Pass area]
-
A.
scenicSectionName
Indicates the specific name assigned to a scenic section or segment within a larger route, area, or context.
-
B.
hasScenicSectionAt
chosen
Indicates that a route, path, or area contains a specific segment or location that is considered scenic at that point.
-
C.
hasScenicSectionNear
Indicates that one location includes a visually appealing or picturesque segment situated close to another specified location.
-
D.
hasScenicSections
Indicates that a route, path, or area contains segments that are visually attractive or offer notable scenic views.
-
E.
isScenicStartingPointFor
Indicates that a location serves as an especially picturesque or visually appealing starting point for a route, journey, or activity.
- 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_6a368251b7148190a82672a8e7d57ad6 |
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.