Triple
T28435506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manang |
E715250
|
entity |
| Predicate | roleOnTrek |
P137851
|
FINISHED |
| Object | logistical hub on Annapurna Circuit |
—
|
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: logistical hub on Annapurna Circuit | Statement: [Manang, roleOnTrek, logistical hub on Annapurna Circuit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOnTrek Context triple: [Manang, roleOnTrek, logistical hub on Annapurna Circuit]
-
A.
roleInExpedition
Indicates the specific function, duty, or position an entity holds within the context of a particular expedition.
-
B.
travelRouteRole
chosen
Indicates the specific functional role an entity plays within a travel route, such as origin, destination, or intermediate stop.
-
C.
roleAtOutwild
Indicates that an entity holds or performs a specific role or position within the organization or context named Outwild.
-
D.
roleOn
Indicates that an entity holds or performs a specific role or function within another entity, context, or activity.
-
E.
tourRole
Indicates the specific function, capacity, or responsibility an entity has within the context of a tour.
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 1:42 a.m.