Triple
T26743461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jorethang |
E674327
|
entity |
| Predicate | hasRoadLinkType |
P74765
|
FINISHED |
| Object | regional road network |
—
|
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: regional road network | Statement: [Jorethang, hasRoadLinkType, regional road network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadLinkType Context triple: [Jorethang, hasRoadLinkType, regional road network]
-
A.
isKeyRoadLinkBetween
Indicates that a road segment functions as a primary connecting link between two specific locations or road network elements.
-
B.
hasRoadNetworkType
chosen
Indicates the type or classification of road network associated with or present in an entity.
-
C.
hasRoadComponent
Indicates that something includes, contains, or is composed of a specific road-related part or element.
-
D.
hasRoadJunctionType
Indicates that a road junction has a specific type or classification (e.g., roundabout, intersection, interchange).
-
E.
hasRoadClass
Indicates that a road segment is assigned to a particular classification or category based on its type or functional importance.
- 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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 27, 2026, 3:50 a.m.