Triple

T29844273
Position Surface form Disambiguated ID Type / Status
Subject Tiraspol Airport E757886 entity
Predicate hasInfrastructureCondition P197820 FINISHED
Object partly deteriorated 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: partly deteriorated | Statement: [Tiraspol Airport, hasInfrastructureCondition, partly deteriorated]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasInfrastructureCondition
Context triple: [Tiraspol Airport, hasInfrastructureCondition, partly deteriorated]
  • A. hasInfrastructureAbove
    Indicates that one entity’s infrastructure is physically located above or over another entity.
  • B. hasInfrastructureType
    Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
  • C. hasAccessInfrastructure
    Indicates that an entity is equipped with or connected to the physical or technical infrastructure necessary to access a particular service, resource, or network.
  • D. hasInfrastructurePolicy
    Indicates that an entity has established rules, plans, or guidelines governing the development, management, or use of infrastructure.
  • E. hasInfrastructurePeriod
    Indicates the time period during which a particular piece of infrastructure exists, is in use, or is valid.
  • 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_69f224593f6c81908785a560fe659f58 completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69feafa1ba0081909013800b85a9f613 completed May 9, 2026, 3:53 a.m.
PD Predicate disambiguation batch_69feae58d62c81909d031f3df8992883 completed May 9, 2026, 3:47 a.m.
PDg Predicate description generation batch_69feafa0acd881908bb6c01635b5537a completed May 9, 2026, 3:53 a.m.
Created at: April 29, 2026, 5:41 p.m.