Triple
T20166138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TurboExpress |
E491828
|
entity |
| Predicate | mediaFormat |
P131
|
FINISHED |
| Object | HuCard |
—
|
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: HuCard | Statement: [TurboExpress, mediaFormat, HuCard]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HuCard Context triple: [TurboExpress, mediaFormat, HuCard]
-
A.
HuCard
chosen
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.
-
B.
Leap Card
Leap Card is a reusable, contactless smart card used for paying public transport fares across Dublin and other parts of Ireland.
-
C.
Clubcard
Clubcard is Tesco’s customer loyalty program that offers members points, discounts, and personalized offers on their shopping.
-
D.
Q Card
Q Card is a contactless smart fare card used for paying public transportation fares in the Houston METRO transit system.
-
E.
HOLO card
The HOLO card is a contactless smart fare card used for paying transit fares on Honolulu’s public transportation system.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e668442d2c81908bb1a0fac9895b5e |
completed | April 20, 2026, 5:54 p.m. |
Created at: April 11, 2026, 11:35 p.m.