Triple

T8141812
Position Surface form Disambiguated ID Type / Status
Subject Medallion Qualification Miles E190114 entity
Predicate rolloverEligible P84 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: [Medallion Qualification Miles, rolloverEligible, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: rolloverEligible
Context triple: [Medallion Qualification Miles, rolloverEligible, yes]
  • A. alsoEligible
    Indicates that an entity qualifies for an additional option, status, or benefit beyond its primary or initial eligibility.
  • B. eligibilityLevel
    Indicates the degree or tier of qualification an entity has for a given benefit, service, or status.
  • C. positionEligible
    Indicates that an entity is qualified or permitted to hold or be assigned to a particular position or role.
  • D. eligibleOn
    Indicates the date or condition from which something qualifies to begin or be considered valid or applicable.
  • E. eligibility chosen
    Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
  • 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_69ca82bd9900819099477cdc2eb4244f completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb4442299881909db56f7475cbb99a completed March 31, 2026, 3:49 a.m.
PD Predicate disambiguation batch_69cb369c0d0481908762c488d7f77e74 completed March 31, 2026, 2:51 a.m.
Created at: March 30, 2026, 5:36 p.m.