Triple
T24933763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metcard |
E623257
|
entity |
| Predicate | ticketTypesIncluded |
P70950
|
FINISHED |
| Object | single trip tickets |
—
|
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: single trip tickets | Statement: [Metcard, ticketTypesIncluded, single trip tickets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketTypesIncluded Context triple: [Metcard, ticketTypesIncluded, single trip tickets]
-
A.
ticketIncludes
chosen
Indicates that a particular ticket grants access to, contains, or covers the specified item, service, or component.
-
B.
ticketTypeAccepted
Indicates that a particular type of ticket is valid for use or accepted in a given context or by a given entity.
-
C.
ticketTypeExample
Indicates that an entity serves as an example or illustrative instance of a particular ticket type.
-
D.
ticketFormat
Indicates the specific structure, layout, or template in which a ticket is represented or issued.
-
E.
ticketingCompatibleWith
Indicates that two systems, services, or components can interoperate or be used together within the same ticketing or reservation workflow without conflict.
- 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.