Triple

T2770752
Position Surface form Disambiguated ID Type / Status
Subject CNN Airport Network E61448 entity
Predicate locationRequirement P43060 FINISHED
Object not available in homes 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: not available in homes | Statement: [CNN Airport Network, locationRequirement, not available in homes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locationRequirement
Context triple: [CNN Airport Network, locationRequirement, not available in homes]
  • A. appointmentRequirement
    Indicates that a particular action, service, or interaction can only occur if an appointment has been scheduled or a specified appointment condition is met.
  • B. occupancyRequirement
    Indicates that a condition specifies how many or which entities must be present in or using a particular space or resource.
  • C. bookingRequirement
    Indicates that a particular condition, rule, or prerequisite must be satisfied in order to make or confirm a booking.
  • D. hasResidentialRequirement
    Indicates that an entity is subject to a condition requiring residence in a specified place or under specified living arrangements.
  • E. recruitmentLocation
    Indicates the place or geographic area where the recruitment or hiring of individuals occurs.
  • 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_69ab4b7cd13481909174bca9809ed259 completed March 6, 2026, 9:47 p.m.
NER Named-entity recognition batch_69abddceb9d88190961e30d521a21552 completed March 7, 2026, 8:11 a.m.
PD Predicate disambiguation batch_69abdcfed608819080988e93df7bdf7c completed March 7, 2026, 8:08 a.m.
PDg Predicate description generation batch_69abddcc348081908b5f760899389d4f completed March 7, 2026, 8:11 a.m.
Created at: March 6, 2026, 9:57 p.m.