Triple

T12664313
Position Surface form Disambiguated ID Type / Status
Subject Sendai Airport E302506 entity
Predicate hasQuarantine P106090 FINISHED
Object yes 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: yes | Statement: [Sendai Airport, hasQuarantine, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasQuarantine
Context triple: [Sendai Airport, hasQuarantine, yes]
  • A. wasQuarantineStationFor
    Indicates that a location served as a designated quarantine facility for a particular group of people, animals, or goods.
  • B. hasContactTracingActivities
    Indicates that an entity engages in or is associated with activities related to tracking and monitoring contacts of individuals, typically for disease exposure or transmission analysis.
  • C. hasCountryOfRisk
    Indicates that an entity is associated with a country where it faces significant exposure, vulnerability, or potential risk.
  • D. hasHealthCode
    Indicates that an entity is associated with a specific health-related classification or status code.
  • E. hasVaccine
    Indicates that one entity possesses, provides, or is associated with a specific vaccine in relation to another entity.
  • 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_69d7bded71a88190bb76e2413af9ea66 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d9617e030881908444743b8a7e0d75 completed April 10, 2026, 8:45 p.m.
PD Predicate disambiguation batch_69d960b78ce8819091f15dd5013e6da5 completed April 10, 2026, 8:42 p.m.
PDg Predicate description generation batch_69d96179c7648190a05a13991d62bebb completed April 10, 2026, 8:45 p.m.
Created at: April 9, 2026, 5:19 p.m.