Triple
T832414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dubai Bus |
E17993
|
entity |
| Predicate | fareSystem |
P395
|
FINISHED |
| Object | Nol card |
E74359
|
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: Nol card | Statement: [Dubai Bus, fareSystem, Nol card]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nol card Context triple: [Dubai Bus, fareSystem, Nol card]
-
A.
Nol card
chosen
The Nol card is a rechargeable smart card used for paying fares across Dubai’s public transportation network, including metro, buses, trams, and water buses.
-
B.
CharlieCard
The CharlieCard is a reusable contactless smart card used to pay fares on Boston's MBTA public transit system.
-
C.
Cardiac Cards
Cardiac Cards is a nickname for the former St. Louis Cardinals NFL team, referencing their dramatic, late-game comebacks and close finishes.
-
D.
NOK
NOK is the official currency code for the Norwegian krone, the national currency of Norway.
-
E.
Presto card
The Presto card is a reloadable smart card used for paying public transit fares across the Greater Toronto and Hamilton Area and other regions in Ontario, Canada.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abb647988190950e1790bcfa60a5 |
completed | March 1, 2026, 9:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a76d9991488190808adb29d3ad6273 |
completed | March 3, 2026, 11:24 p.m. |
Created at: March 1, 2026, 7:38 p.m.