Triple
T24933787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metcard |
E623257
|
entity |
| Predicate | hadFullFareOption |
P132047
|
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, hadFullFareOption, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadFullFareOption Context triple: [Metcard, hadFullFareOption, yes]
-
A.
hasCheckedBaggage
Indicates that an entity is associated with baggage that has been checked in for transport, typically for a trip or flight.
-
B.
hasTicketOption
chosen
Indicates that an entity offers or is associated with a particular ticket choice or type as an available option.
-
C.
hadSeatType
Indicates that an entity was assigned or associated with a specific type or category of seat.
-
D.
hasFarePaidArea
Indicates that an entity includes or is associated with a zone where access is restricted to users who have paid a fare.
-
E.
hasPassengerAirlineService
Indicates that a location or facility is served by scheduled passenger airline flights.
- 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_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. |
Created at: April 18, 2026, 5:30 a.m.