Triple

T9675979
Position Surface form Disambiguated ID Type / Status
Subject Lentekhi E234152 entity
Predicate isTouristTransitPoint P89568 FINISHED
Object true 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: true | Statement: [Lentekhi, isTouristTransitPoint, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isTouristTransitPoint
Context triple: [Lentekhi, isTouristTransitPoint, true]
  • A. isMajorTransitPointFor
    Indicates that a location serves as a primary hub or key node for the movement or transfer of people, goods, or vehicles within a transportation network.
  • B. isPublicTransportStation
    Indicates that a location functions as a station or stop used by public transportation services such as buses, trains, trams, or subways.
  • C. wasTransitPointOn
    Indicates that something served as an intermediate stop or passage location along a specified route, journey, or transport path.
  • D. isPartOfTouristArea
    Indicates that one entity is located within or belongs to a designated tourist area or tourist-focused region.
  • E. isTransportHubType
    Indicates that something serves as or belongs to a particular category of transport hub (such as a station, port, or terminal).
  • F. None of above. chosen

Provenance (4 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_69ca848f55e48190b3f67252571c3d45 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9c6ed62081908863f2ea0e98961a completed April 1, 2026, 10:30 p.m.
PD Predicate disambiguation batch_69ccd5b5d40c8190850ad7a351445f32 completed April 1, 2026, 8:22 a.m.
PDg Predicate description generation batch_69ccd9408c848190b84dd74d87f76273 completed April 1, 2026, 8:37 a.m.
Created at: March 30, 2026, 8:15 p.m.