Triple
T27524103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AH1 |
E694787
|
entity |
| Predicate | isMajorRouteInNetwork |
P89731
|
FINISHED |
| Object | Asian Highway Network |
—
|
NE NERFINISHED |
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 Network | Statement: [AH1, isMajorRouteInNetwork, Asian Highway Network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorRouteInNetwork Context triple: [AH1, isMajorRouteInNetwork, Asian Highway Network]
-
A.
isMajorRouteInSystem
chosen
Indicates that a route functions as a primary or significant corridor within a specified transportation or network system.
-
B.
isMajorRouteThrough
Indicates that a route serves as a primary or significant pathway passing through a specified area or location.
-
C.
isMajorRouteFor
Indicates that something serves as a primary or heavily used pathway or channel for the movement or flow of something else.
-
D.
hasMajorRouteType
Indicates that an entity is associated with a primary classification of transportation route (such as highway, rail line, or other major route type).
-
E.
isMajorBusinessRoute
Indicates that a route serves as a primary corridor for significant commercial or business-related traffic and activities.
- 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 27, 2026, 1:23 p.m.