Triple
T29648578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamu |
E756071
|
entity |
| Predicate | roadLinkType |
P131761
|
FINISHED |
| Object | Asian Highway corridor segment |
—
|
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: Asian Highway corridor segment | Statement: [Tamu, roadLinkType, Asian Highway corridor segment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadLinkType Context triple: [Tamu, roadLinkType, Asian Highway corridor segment]
-
A.
roadType
Indicates the classification or category of a road based on its functional or physical characteristics.
-
B.
roadAssociatedWith
chosen
Indicates that there is a relevant connection or linkage between a road and another entity, such as use, location, function, or impact.
-
C.
linkedByRoadTo
Indicates that two locations are directly connected to each other by a road suitable for travel.
-
D.
roadJunctionIncludes
Indicates that a road junction spatially contains or encompasses a specific road segment or related roadway element as part of its structure.
-
E.
roadNumberType
Indicates the classification or type category assigned to a road’s identifying number (e.g., highway, route, local road).
- 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f66f21ff708190b13e801de63bf603 |
completed | May 2, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:51 p.m.