Triple
T12896181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kabul–Mazar-i-Sharif road |
E308498
|
entity |
| Predicate | importanceForTrade |
P74963
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Kabul–Mazar-i-Sharif road, importanceForTrade, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importanceForTrade Context triple: [Kabul–Mazar-i-Sharif road, importanceForTrade, high]
-
A.
hasCommercialImportance
chosen
Indicates that something possesses economic or business value significant enough to impact trade, revenue, or market activity.
-
B.
shippingLaneImportance
Indicates the degree to which a particular shipping lane is considered significant or critical relative to other possible routes.
-
C.
isImportantFor
Indicates that something holds significant value, relevance, or necessity in relation to something else.
-
D.
usedForTradeBetween
Indicates that something serves as a medium, instrument, or basis for trade or exchange between two or more parties.
-
E.
usedInInternationalTrade
Indicates that something participates as a good, service, or instrument in commercial exchanges between different countries.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9717d859481908957510babac2d69 |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:40 p.m.