Triple
T32443935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thorung Phedi |
E829091
|
entity |
| Predicate | servesTrekkersTo |
P124592
|
FINISHED |
| Object | Muktinath |
—
|
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: Muktinath | Statement: [Thorung Phedi, servesTrekkersTo, Muktinath]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesTrekkersTo Context triple: [Thorung Phedi, servesTrekkersTo, Muktinath]
-
A.
servesTravelersTo
chosen
Indicates a relationship where one entity provides services, assistance, or accommodations specifically directed toward travelers heading to a particular destination.
-
B.
intendedToServe
Indicates that one entity was designed, planned, or purposed specifically to benefit, assist, or fulfill the needs of another entity.
-
C.
servesCamp
Indicates that an entity provides services, support, or functions in a role dedicated to a particular camp or camp-related organization.
-
D.
servesProduct
Indicates that one entity provides or offers a particular product to others, typically in a commercial or service context.
-
E.
servesResortArea
Indicates that one entity provides services or operational support to a resort area.
- 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff27b125948190aced0fe0189fd39a |
completed | May 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69ff26c30a0481909ef6a54ded851e42 |
completed | May 9, 2026, 12:21 p.m. |
Created at: May 1, 2026, 12:55 a.m.