Triple
T21125845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dublin Area Rapid Transit |
E520553
|
entity |
| Predicate | fareMedium |
P1303
|
FINISHED |
| Object | Leap Card |
E883825
|
NE 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: Leap Card | Statement: [Dublin Area Rapid Transit, fareMedium, Leap Card]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leap Card Context triple: [Dublin Area Rapid Transit, fareMedium, Leap Card]
-
A.
Leap Card
chosen
Leap Card is a reusable, contactless smart card used for paying public transport fares across Dublin and other parts of Ireland.
-
B.
Clubcard
Clubcard is Tesco’s customer loyalty program that offers members points, discounts, and personalized offers on their shopping.
-
C.
Q Card
Q Card is a contactless smart fare card used for paying public transportation fares in the Houston METRO transit system.
-
D.
Go-To Card
The Go-To Card is a reusable, contactless smart card used to pay fares on the Minneapolis–Saint Paul METRO transit system.
-
E.
Karta
Karta was a former administrative district or leadership term that historically governed the area later known as Plered.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69e0b50a623881909c0bbaf4f2c055e7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72238cf708190a4676c40deea2e46 |
completed | April 21, 2026, 7:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0965eb985081908e83e65d104e25ee |
completed | May 17, 2026, 6:53 a.m. |
Created at: April 16, 2026, 2:56 p.m.