Triple
T38626189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MBTA tokens |
E937016
|
entity |
| Predicate | farePaymentFor |
P186106
|
FINISHED |
| Object | Boston public transit |
—
|
LITERAL 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: Boston public transit | Statement: [MBTA tokens, farePaymentFor, Boston public transit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: farePaymentFor Context triple: [MBTA tokens, farePaymentFor, Boston public transit]
-
A.
feePaidIn
Indicates that a specified fee has been paid in a particular currency or payment medium.
-
B.
fare
Indicates the price or cost required for a person or thing to be transported by a particular mode of travel or service.
-
C.
fareIntegration
Indicates that multiple transportation services or modes share a coordinated fare system, allowing passengers to use a single payment or ticket across them.
-
D.
feeAppliesTo
chosen
Indicates that a particular fee is charged in connection with, or is applicable to, a specified item, service, or transaction.
-
E.
fareCollectionType
Indicates the method or system used to collect fares or payments for a service.
- F. None of above.
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_69f76ed403208190b862dc795171353f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.