Triple

T24933786
Position Surface form Disambiguated ID Type / Status
Subject Metcard E623257 entity
Predicate hadConcessionOption P157252 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: [Metcard, hadConcessionOption, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hadConcessionOption
Context triple: [Metcard, hadConcessionOption, yes]
  • A. hasConcessions
    Indicates that one entity provides or contains concession facilities, services, or rights (such as food, drink, or merchandise sales) for another entity or within a given context.
  • B. concessionFor
    Indicates a relationship where one party grants or yields something—such as rights, privileges, or resources—to another, often as part of a negotiation or agreement.
  • C. concessionBy
    Indicates that one party grants, yields, or makes allowances to another, often accepting a demand, point, or condition despite initial opposition or differing interests.
  • D. concessionExtended
    Indicates that one party has granted or prolonged a special allowance, discount, or favorable term to another party.
  • E. demandedConcessionTo
    Indicates that one party insisted another party grant a concession, typically as a condition or requirement in a negotiation or conflict.
  • 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_69e2fac6b5a48190a1c38857f00915a9 completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f423b654e48190b9a073a67cbf82f3 completed May 1, 2026, 3:53 a.m.
PD Predicate disambiguation batch_69f4210130d08190ae30b7943f7a0bbc completed May 1, 2026, 3:41 a.m.
PDg Predicate description generation batch_69f423637bec8190a1701421ac86a3b7 completed May 1, 2026, 3:52 a.m.
Created at: April 18, 2026, 5:30 a.m.