Triple
T17407748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aloha Stadium rail station |
E423263
|
entity |
| Predicate | fareSystem |
P395
|
FINISHED |
| Object | HOLO card |
—
|
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: HOLO card | Statement: [Aloha Stadium rail station, fareSystem, HOLO card]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HOLO card Context triple: [Aloha Stadium rail station, fareSystem, HOLO card]
-
A.
HOLO card
chosen
The HOLO card is a contactless smart fare card used for paying transit fares on Honolulu’s public transportation system.
-
B.
HOLO
HOLO is a brand associated with HOLO cards, typically used for contactless payment or access in transit and related services.
-
C.
HuCard
HuCard is a thin, credit card–sized ROM cartridge used to store and play games on NEC’s TurboGrafx-16/PC Engine video game consoles.
-
D.
HSL card
The HSL card is a rechargeable smart travel card used to pay fares on public transportation services in the Helsinki region.
-
E.
Leap Card
Leap Card is a reusable, contactless smart card used for paying public transport fares across Dublin and other parts of Ireland.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43b08d5a881909e7a5b2ae2c60898 |
completed | April 19, 2026, 2:16 a.m. |
Created at: April 10, 2026, 5:46 a.m.