Triple
T15599951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lava Tower |
E375004
|
entity |
| Predicate | typicalItineraryRole |
P24306
|
FINISHED |
| Object | high point for climb-high-sleep-low strategy |
—
|
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: high point for climb-high-sleep-low strategy | Statement: [Lava Tower, typicalItineraryRole, high point for climb-high-sleep-low strategy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalItineraryRole Context triple: [Lava Tower, typicalItineraryRole, high point for climb-high-sleep-low strategy]
-
A.
travelRole
Indicates the specific role or capacity an entity has in relation to a travel activity or journey (e.g., traveler, guide, driver).
-
B.
tourWith
Indicates that one entity accompanies another on a tour, sharing the same itinerary or guided experience.
-
C.
travelRouteOf
Indicates the path or itinerary that an entity follows or uses when traveling from one location to another.
-
D.
tourOf
Indicates that one entity serves as a guided or organized visit through another entity, typically for exploration, education, or sightseeing.
-
E.
roleInExpedition
chosen
Indicates the specific function, duty, or position an entity holds within the context of a particular expedition.
- 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_69d85cce25008190b13b52745fbd719b |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e621fc4819097e8e85e7ddfdc6c |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:12 a.m.