Triple
T28336558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jomsom–Muktinath trek |
E717689
|
entity |
| Predicate | hasCommonAccessMode |
P6865
|
FINISHED |
| Object | flight to Jomsom |
—
|
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: flight to Jomsom | Statement: [Jomsom–Muktinath trek, hasCommonAccessMode, flight to Jomsom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonAccessMode Context triple: [Jomsom–Muktinath trek, hasCommonAccessMode, flight to Jomsom]
-
A.
hasAccessMode
chosen
Indicates the type or method of access that one entity is permitted to use with respect to another entity or resource.
-
B.
hasHumanAccess
Indicates that a human is able to access, use, or interact with the referenced entity or resource.
-
C.
hasAccessModel
Indicates that one entity is permitted to use, interact with, or retrieve a particular model controlled by another entity or system.
-
D.
hasAccessibleAccess
Indicates that an entity provides a form of access that is usable and reachable under defined accessibility conditions or standards.
-
E.
hasTypicalAccess
Indicates that one entity normally or customarily has the ability, permission, or means to access or use another entity.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69ff9b1ad27081908f8a492396950795 |
completed | May 9, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69ff9a6354c48190ae21070c1424cb7a |
completed | May 9, 2026, 8:34 p.m. |
Created at: April 28, 2026, 12:36 a.m.