Triple
T12136071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Ramón station |
E289059
|
entity |
| Predicate | fareCard |
P5430
|
FINISHED |
| Object | Bip! card |
E284705
|
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: Bip! card | Statement: [San Ramón station, fareCard, Bip! card]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bip! card Context triple: [San Ramón station, fareCard, Bip! card]
-
A.
Bip! card
chosen
The Bip! card is a rechargeable contactless smart card used to pay fares across Santiago, Chile’s integrated public transportation system.
-
B.
BIP
BIP was the abbreviation for the Bureau of Information and Propaganda, a key Polish underground organization responsible for information, education, and psychological operations during World War II.
-
C.
Leap Card
Leap Card is a reusable, contactless smart card used for paying public transport fares across Dublin and other parts of Ireland.
-
D.
Beep card
The Beep card is a contactless smart card used as a stored-value ticketing system for public transportation and related services in the Philippines.
-
E.
ConnectCard
ConnectCard is a reusable smart fare card used by Pittsburgh Regional Transit riders to pay for public transportation across the Pittsburgh area.
- 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_69d6ab4b5e4c81909950b17151eb0951 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9158dd00c819082651891898b91bb |
completed | April 10, 2026, 3:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f68eab98819086a480a90312c3fe |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 8, 2026, 9:49 p.m.