Triple
T17210647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Line (Miami Metrorail) |
E417718
|
entity |
| Predicate | fareSystem |
P395
|
FINISHED |
| Object | EASY Ticket |
E311297
|
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: EASY Ticket | Statement: [Green Line (Miami Metrorail), fareSystem, EASY Ticket]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EASY Ticket Context triple: [Green Line (Miami Metrorail), fareSystem, EASY Ticket]
-
A.
EASY Ticket
chosen
EASY Ticket is a rechargeable smart fare card used by Miami-Dade Metrorail and related transit services for convenient electronic payment of rides.
-
B.
Breeze Ticket
Breeze Ticket is MARTA’s reloadable smart fare card used for paying bus and rail fares in the Atlanta public transit system.
-
C.
CharlieTicket
CharlieTicket is a reusable paper smart card used for paying fares on Boston’s MBTA public transit system.
-
D.
EASY Card
The EASY Card is a contactless smart card used as a stored-value payment method for public transit services in the Miami-Dade area.
-
E.
Weekend Ticket
Weekend Ticket is a discounted Belgian train fare offered by NMBS/SNCB that allows passengers to make return journeys at reduced prices over the weekend.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42dc4792081909443df7937768ede |
completed | April 19, 2026, 1:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a015fe217308190b6ae1e98d0c421e4 |
completed | May 11, 2026, 4:49 a.m. |
Created at: April 10, 2026, 5:38 a.m.