Triple

T1459269
Position Surface form Disambiguated ID Type / Status
Subject Presto card E31472 entity
Predicate supportsConcessionFares P15903 FINISHED
Object true 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: true | Statement: [Presto card, supportsConcessionFares, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsConcessionFares
Context triple: [Presto card, supportsConcessionFares, true]
  • 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. farePolicySupport chosen
    Indicates that there is a policy in place governing fares (such as prices, discounts, or rules) that is recognized, enabled, or supported in the given context.
  • C. hasFareControlIntegrationSince
    Indicates that a fare control system has been integrated with another system or entity starting from a specific point in time.
  • D. usesFareMedium
    Indicates that an entity employs a particular fare medium (such as a ticket, card, or pass) as the method of payment or validation for a trip or service.
  • E. fareSystem
    Indicates a relationship where a system is used to determine, collect, or manage fares or payments for transportation or similar services.
  • 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_69a49917dfc081909acdbdf5d684f1ef completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c59c1c288190be08064f2d351b2b completed March 1, 2026, 11:02 p.m.
PD Predicate disambiguation batch_69a4c47ec5108190b1772237f2e5d90b completed March 1, 2026, 10:58 p.m.
Created at: March 1, 2026, 8 p.m.