Triple

T14743947
Position Surface form Disambiguated ID Type / Status
Subject Y class E346417 entity
Predicate oftenRequiredFor P107344 FINISHED
Object certain corporate or government flexible travel policies 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: certain corporate or government flexible travel policies | Statement: [Y class, oftenRequiredFor, certain corporate or government flexible travel policies]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: oftenRequiredFor
Context triple: [Y class, oftenRequiredFor, certain corporate or government flexible travel policies]
  • A. isOftenRequiredFor chosen
    Indicates that one entity is frequently needed or commonly necessary for the occurrence, use, or success of another entity or activity.
  • B. requiredTo
    Indicates that one entity has an obligation or necessity to perform an action or satisfy a condition in relation to another entity or context.
  • C. requiredToProvide
    Indicates that one entity has an obligation or duty to supply or furnish something to another entity.
  • D. isNotRequiredFor
    Indicates that one entity is not necessary or mandatory for the existence, occurrence, validity, or completion of another entity or process.
  • E. requiredBy
    Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
  • 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_69d822e6f1c88190bc494d491a907114 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dec7d002708190a32a4a45e96fc389 completed April 14, 2026, 11:03 p.m.
PD Predicate disambiguation batch_69de8bf9331481909582045cd567d91f completed April 14, 2026, 6:48 p.m.
Created at: April 10, 2026, 1:30 a.m.