Triple
T22680611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sapito Falls |
E560469
|
entity |
| Predicate | isPartOfItinerary |
P6309
|
FINISHED |
| Object | Canaima Lagoon boat excursions |
—
|
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: Canaima Lagoon boat excursions | Statement: [Sapito Falls, isPartOfItinerary, Canaima Lagoon boat excursions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfItinerary Context triple: [Sapito Falls, isPartOfItinerary, Canaima Lagoon boat excursions]
-
A.
isPartOfTourDocument
Indicates that a given document belongs to, or is included within, a specific tour-related collection or itinerary.
-
B.
isPartOfRoute
chosen
Indicates that something (such as a segment, stop, or step) belongs to and is contained within a larger route.
-
C.
isPartOfAttraction
Indicates that something is a component or sub-element within a larger attraction or point of interest.
-
D.
journeyParticipation
Indicates that an entity takes part in, accompanies, or is otherwise involved in a specific journey or trip.
-
E.
travelRouteContext
Indicates the contextual details (such as purpose, conditions, or circumstances) under which a particular travel route is taken or defined.
- 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1786027648190972d1b0bbe81ed13 |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:11 p.m.