Triple
T4490291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prometheus Cave |
E107354
|
entity |
| Predicate | hasTourRoute |
P7952
|
FINISHED |
| Object | guided tours |
—
|
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: guided tours | Statement: [Prometheus Cave, hasTourRoute, guided tours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTourRoute Context triple: [Prometheus Cave, hasTourRoute, guided tours]
-
A.
hasTouristRoute
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
-
B.
hasTour
chosen
Indicates that an entity offers, includes, or is associated with a tour experience or guided visit.
-
C.
hasRecreationalRoute
Indicates that an entity is associated with or includes a route intended for recreational activities such as walking, cycling, or hiking.
-
D.
hasTourismFunction
Indicates that an entity serves a role or purpose related to tourism, such as attracting, accommodating, or providing services to tourists.
-
E.
touringActivity
Indicates an activity where an entity travels from place to place, typically for visiting, performing, or sightseeing purposes.
- 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_69bd43f84f788190a1383579c4a595be |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd556d29f08190bab1e872dd7e819f |
completed | March 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69bd5213e3d0819094b026989e686f01 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 12:59 p.m.