Triple

T21557893
Position Surface form Disambiguated ID Type / Status
Subject Rayak E531939 entity
Predicate hasAirBaseFunction P144235 FINISHED
Object Lebanese Air Force operations 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: Lebanese Air Force operations | Statement: [Rayak, hasAirBaseFunction, Lebanese Air Force operations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAirBaseFunction
Context triple: [Rayak, hasAirBaseFunction, Lebanese Air Force operations]
  • A. isAirBase
    Indicates that the subject entity functions as a military air base, i.e., a facility used for operating, housing, and supporting aircraft and related activities.
  • B. usesAirbase
    Indicates that one entity operates from, accesses, or conducts activities at a particular airbase.
  • C. usesAirbaseType
    Indicates that one entity makes use of, operates from, or is otherwise functionally associated with a particular type or category of airbase.
  • D. hasReuseOfAirBase
    Indicates that one entity makes use of an air base that is originally owned, operated, or primarily used by another entity.
  • E. hasTacticalAviationFacilities
    Indicates that an entity possesses or hosts infrastructure and resources specifically designated for tactical aviation operations.
  • 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_69e0c460232c81908de2c3819d17c00e completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69eed2e14af88190bc70b4d0f3453aac completed April 27, 2026, 3:07 a.m.
PD Predicate disambiguation batch_69e6320766308190ba5dca2f7c826aa4 completed April 20, 2026, 2:02 p.m.
PDg Predicate description generation batch_69e633bf34c481909925d8dc1a633a65 completed April 20, 2026, 2:10 p.m.
Created at: April 16, 2026, 6:29 p.m.