Triple
T32426149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Yorkshire Metro zone 2 |
E828581
|
entity |
| Predicate | usedByTicket |
P189461
|
FINISHED |
| Object | MetroCard |
—
|
NE NERFINISHED |
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: MetroCard | Statement: [West Yorkshire Metro zone 2, usedByTicket, MetroCard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByTicket Context triple: [West Yorkshire Metro zone 2, usedByTicket, MetroCard]
-
A.
usedForTicketType
Indicates that something is utilized or applicable for a specific type or category of ticket.
-
B.
usesTicketZone
Indicates that an entity’s validity, access, or operation is determined by or restricted to a specific ticket zone.
-
C.
usedInE-tickets
Indicates that something (such as a method, technology, or feature) is employed or applied within the context of electronic tickets (e-tickets).
-
D.
usesTicketValidatorType
Indicates that an entity employs or is associated with a specific type or category of ticket validation device or method.
-
E.
usedInRailwayTickets
Indicates that something is employed or applied in the context of railway tickets, such as their creation, validation, or usage.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: May 1, 2026, 12:54 a.m.