Triple
T145866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CharlieCard |
E3327
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Disability CharlieCard |
E3327
|
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: Disability CharlieCard | Statement: [CharlieCard, hasVariant, Disability CharlieCard]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Disability CharlieCard Context triple: [CharlieCard, hasVariant, Disability CharlieCard]
-
A.
CharlieCard
chosen
The CharlieCard is a reusable contactless smart card used to pay fares on Boston's MBTA public transit system.
-
B.
TAP card
The TAP card is a reusable contactless smart card used to pay fares across public transit systems in the Los Angeles County region.
-
C.
CharlieTicket
CharlieTicket is a reusable paper smart card used for paying fares on Boston’s MBTA public transit system.
-
D.
SmarTrip
SmarTrip is a rechargeable contactless smart card used to pay fares on the Washington, D.C. region’s public transit systems.
-
E.
SEPTA Key
SEPTA Key is a contactless smart fare card and payment system used across Philadelphia’s SEPTA public transit network.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a257ea7eac8190884a53453a9e0dd6 |
completed | Feb. 28, 2026, 2:50 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a2c2763ce481908c12046de9003a84 |
completed | Feb. 28, 2026, 10:24 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.