Triple
T32444834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jiri |
E829113
|
entity |
| Predicate | transportModeToEverestRegion |
P177669
|
FINISHED |
| Object | overland trekking route |
—
|
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: overland trekking route | Statement: [Jiri, transportModeToEverestRegion, overland trekking route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportModeToEverestRegion Context triple: [Jiri, transportModeToEverestRegion, overland trekking route]
-
A.
transportModeTo
Indicates the means or mode of transportation used to travel to a specified destination.
-
B.
modeOfTravelToEverest
chosen
Indicates the means or method by which an entity travels to Mount Everest.
-
C.
transportationRegion
Indicates that one entity serves as, or is associated with, a geographic region relevant to the transportation activities or coverage of another entity.
-
D.
typicalTransportBetweenPeaks
Indicates the usual or most common mode of transportation used to travel between two peaks.
-
E.
transportModeAccess
Indicates that one entity has the ability or permission to use, reach, or be served by a particular mode of transportation.
- 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_69fea5e828cc8190a9b755a645dc56d2 |
completed | May 9, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69fea36443f08190b2aced9b4a0525fd |
completed | May 9, 2026, 3 a.m. |
Created at: May 1, 2026, 12:55 a.m.