Triple

T38346085
Position Surface form Disambiguated ID Type / Status
Subject Türkmendemirýollary E1041543 entity
Predicate hasTrackOwnership P202247 FINISHED
Object majority of railway tracks in Turkmenistan 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: majority of railway tracks in Turkmenistan | Statement: [Türkmendemirýollary, hasTrackOwnership, majority of railway tracks in Turkmenistan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTrackOwnership
Context triple: [Türkmendemirýollary, hasTrackOwnership, majority of railway tracks in Turkmenistan]
  • A. ownerOfSomeTrack
    Indicates that an entity has ownership of at least one track (such as a song, audio track, or similar item).
  • B. usesTrackOwnedBy
    Indicates that an entity makes use of a track (e.g., route, path, or rail line) that is owned by another specified entity.
  • C. hasTrack
    Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
  • D. hasTrackageRightsOn
    Indicates that one rail operator is authorized to run its trains over track owned or controlled by another entity.
  • E. trackOwnershipOutcome
    Indicates the result or status of an ownership-tracking process or event between entities.
  • 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_69f76e2ad95481908c920c0e5c1c3e26 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_6a0064f8efa48190956287f548a8057d completed May 10, 2026, 10:59 a.m.
PD Predicate disambiguation batch_6a006471e75c8190adae99bd75e7411b completed May 10, 2026, 10:56 a.m.
PDg Predicate description generation batch_6a0064f8496081908ac3bb4c53ed08aa completed May 10, 2026, 10:59 a.m.
Created at: May 3, 2026, 4:30 p.m.