Triple

T3592899
Position Surface form Disambiguated ID Type / Status
Subject Pago Pago International Airport E76066 entity
Predicate hasRescueAndFirefightingService P464 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: [Pago Pago International Airport, hasRescueAndFirefightingService, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRescueAndFirefightingService
Context triple: [Pago Pago International Airport, hasRescueAndFirefightingService, yes]
  • A. hasFireStation
    Indicates that a location or area contains or is served by a fire station.
  • B. hasEmergencyServices chosen
    Indicates that the subject provides or is equipped with emergency response services (such as police, fire, or medical assistance).
  • C. hasMunicipalService
    Indicates that a municipality provides or is responsible for a specific public service to a given area, facility, or population.
  • D. fireRescue
    Indicates a relationship where one entity performs or is responsible for rescuing people or property from fires or fire-related emergencies involving another entity.
  • E. hasServiceCenter
    Indicates that an entity maintains or is associated with a service center that provides support, repair, or maintenance services.
  • F. None of above.

Provenance (3 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_69ad85d8042081908af94a04c410dec0 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc15bbbcc81908d6cf95f8e70c6ca completed March 8, 2026, 6:35 p.m.
PD Predicate disambiguation batch_69adb83b66708190bb9d2f23d6fd308e completed March 8, 2026, 5:56 p.m.
Created at: March 8, 2026, 3:22 p.m.