Triple
T27799620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thakali |
E702203
|
entity |
| Predicate | traditionalRoute |
P85749
|
FINISHED |
| Object | Kali Gandaki trade route |
—
|
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: Kali Gandaki trade route | Statement: [Thakali, traditionalRoute, Kali Gandaki trade route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalRoute Context triple: [Thakali, traditionalRoute, Kali Gandaki trade route]
-
A.
tradRoutes
chosen
Indicates a relationship where one location serves as a trade route to or from another location, facilitating the movement of goods or commerce between them.
-
B.
primaryRouteThrough
Indicates that one location or path serves as the main or most significant route passing through another location or area.
-
C.
traditionalRule
Indicates that an entity follows, embodies, or is governed by a customary or long-established rule or norm.
-
D.
traditionalOrder
Indicates that entities are arranged or occur according to a customary, historically established sequence or hierarchy.
-
E.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: April 27, 2026, 5:33 p.m.