Triple
T33977808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asian Highway 4 |
E871188
|
entity |
| Predicate | belongsToCorridorType |
P26881
|
FINISHED |
| Object | land transport corridor |
—
|
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: land transport corridor | Statement: [Asian Highway 4, belongsToCorridorType, land transport corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToCorridorType Context triple: [Asian Highway 4, belongsToCorridorType, land transport corridor]
-
A.
corridorType
chosen
Indicates the specific kind or classification of a corridor associated with an entity or location.
-
B.
hasCorridorName
Indicates that an entity is associated with or identified by the name of a specific corridor.
-
C.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
D.
linkedByCorridor
Indicates that two locations are directly connected to each other by a corridor.
-
E.
isPartOfCorridorSystem
Indicates that one entity forms a component or segment within a larger interconnected corridor system.
- 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_69f3499da0188190ab1a4ff06fb06a2a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
Created at: May 1, 2026, 1:50 a.m.