Triple

T34394776
Position Surface form Disambiguated ID Type / Status
Subject Singapore Airlines passengers E882799 entity
Predicate maySelect P136974 FINISHED
Object special meals for dietary requirements 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: special meals for dietary requirements | Statement: [Singapore Airlines passengers, maySelect, special meals for dietary requirements]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: maySelect
Context triple: [Singapore Airlines passengers, maySelect, special meals for dietary requirements]
  • A. canChoose chosen
    Indicates that an entity has the ability or permission to select one option or entity from among alternatives.
  • B. mayReject
    Indicates that one entity has the authority or option to refuse, decline, or not accept another entity or proposal.
  • C. mayForm
    Indicates that one entity has the potential or permission to be combined or configured to create, constitute, or result in another entity or structure.
  • D. mayGrant
    Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
  • E. mayApprove
    Indicates that an entity has the authority or permission to approve another entity or action, but is not required to do so.
  • 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_69f349c1304081909331872829e38106 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f71c35327c8190884f1bfe12bd2cd7 completed May 3, 2026, 9:58 a.m.
PD Predicate disambiguation batch_69f71822d0e88190ac9731c7ae5a4def completed May 3, 2026, 9:40 a.m.
Created at: May 1, 2026, 1:59 a.m.