Triple
T35876694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asian Highway 92 |
E1037383
|
entity |
| Predicate | hasNetworkDesignation |
P201965
|
FINISHED |
| Object | Asian Highway |
—
|
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 | Statement: [Asian Highway 92, hasNetworkDesignation, Asian Highway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNetworkDesignation Context triple: [Asian Highway 92, hasNetworkDesignation, Asian Highway]
-
A.
hasIspDesignation
Indicates that an entity has been assigned a specific Internet Service Provider (ISP) designation or classification.
-
B.
hasRegionDesignation
Indicates that an entity is assigned or associated with a specific regional classification or designation.
-
C.
hasCityDesignatedAs
Indicates that an entity has a specific city formally assigned or designated to it in a particular role or capacity.
-
D.
hasContactDesignation
Indicates that a specified entity serves as the designated contact (e.g., primary or official point of contact) for another entity.
-
E.
hasDesignationNumber
Indicates that an entity is associated with a specific official designation or identification number.
- F. None of above. chosen
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_69f76e1e701c8190a4990d4978ce4fe6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0039c2d5d48190b8ef2c7ef17d8dc5 |
completed | May 10, 2026, 7:54 a.m. |
| PD | Predicate disambiguation | batch_6a0038e525448190a4c815f51595e78d |
completed | May 10, 2026, 7:51 a.m. |
| PDg | Predicate description generation | batch_6a0039c1eec48190963671a5b8c5f631 |
completed | May 10, 2026, 7:54 a.m. |
Created at: May 3, 2026, 4:06 p.m.