Triple
T24678885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ლაგოდეხი |
E611067
|
entity |
| Predicate | ტურისტული_მარშრუტები |
P17534
|
FINISHED |
| Object | წყალვარდნილის მარშრუტები |
—
|
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: წყალვარდნილის მარშრუტები | Statement: [ლაგოდეხი, ტურისტული_მარშრუტები, წყალვარდნილის მარშრუტები]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ტურისტული_მარშრუტები Context triple: [ლაგოდეხი, ტურისტული_მარშრუტები, წყალვარდნილის მარშრუტები]
-
A.
travelRouteContext
Indicates the contextual details (such as purpose, conditions, or circumstances) under which a particular travel route is taken or defined.
-
B.
travelRouteOf
Indicates the path or itinerary that an entity follows or uses when traveling from one location to another.
-
C.
hasTouristRoute
chosen
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
-
D.
tourismCorridor
Indicates a designated route or area that links multiple destinations to facilitate and promote tourism-related movement and activities between them.
-
E.
tourOf
Indicates that one entity serves as a guided or organized visit through another entity, typically for exploration, education, or sightseeing.
- 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_69e2c4d5c2dc8190ac857dea25ec6ce9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 3:08 a.m.