Triple
T21014638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro (West Yorkshire) |
E517640
|
entity |
| Predicate | usesTicketingScheme |
P3383
|
FINISHED |
| Object |
MCard
MCard is a smart, multi-operator public transport ticketing card used across West Yorkshire for buses and trains.
|
E1461808
|
NE FINISHED |
How this triple was built (4 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: MCard | Statement: [Metro (West Yorkshire), usesTicketingScheme, MCard]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MCard Context triple: [Metro (West Yorkshire), usesTicketingScheme, MCard]
-
A.
Metcard
Metcard was Melbourne’s former magnetic stripe ticketing system used for public transport before the introduction of the Myki smartcard.
-
B.
Q Card
Q Card is a contactless smart fare card used for paying public transportation fares in the Houston METRO transit system.
-
C.
ConnectCard
ConnectCard is a reusable smart fare card used by Pittsburgh Regional Transit riders to pay for public transportation across the Pittsburgh area.
-
D.
Credo Card
Credo Card is a core service philosophy tool used by The Ritz-Carlton Hotel Company to communicate and reinforce its brand standards, values, and commitment to exceptional guest service among employees.
-
E.
CharlieCard
The CharlieCard is a reusable contactless smart card used to pay fares on Boston's MBTA public transit system.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: MCard Triple: [Metro (West Yorkshire), usesTicketingScheme, MCard]
Generated description
MCard is a smart, multi-operator public transport ticketing card used across West Yorkshire for buses and trains.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: MCard Target entity description: MCard is a smart, multi-operator public transport ticketing card used across West Yorkshire for buses and trains.
-
A.
Metcard
Metcard was Melbourne’s former magnetic stripe ticketing system used for public transport before the introduction of the Myki smartcard.
-
B.
Q Card
Q Card is a contactless smart fare card used for paying public transportation fares in the Houston METRO transit system.
-
C.
ConnectCard
ConnectCard is a reusable smart fare card used by Pittsburgh Regional Transit riders to pay for public transportation across the Pittsburgh area.
-
D.
Credo Card
Credo Card is a core service philosophy tool used by The Ritz-Carlton Hotel Company to communicate and reinforce its brand standards, values, and commitment to exceptional guest service among employees.
-
E.
CharlieCard
The CharlieCard is a reusable contactless smart card used to pay fares on Boston's MBTA public transit system.
- F. None of above. chosen
Provenance (5 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_69e0b50262b081909bc488937145eb73 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc5764188190829de6f5abd6e00f |
completed | April 21, 2026, 4:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a093b6369fc81909ff15a48a8a640e2 |
completed | May 17, 2026, 3:52 a.m. |
| NEDg | Description generation | batch_6a093ed7f68c8190b175251a158cbcc1 |
completed | May 17, 2026, 4:06 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a093f3ba1f88190ae07076c83bd0517 |
completed | May 17, 2026, 4:08 a.m. |
Created at: April 16, 2026, 1:54 p.m.