Triple
T33929795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogers Avenue station |
E869855
|
entity |
| Predicate | fareControlCode |
P177919
|
FINISHED |
| Object | ROG |
—
|
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: ROG | Statement: [Rogers Avenue station, fareControlCode, ROG]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareControlCode Context triple: [Rogers Avenue station, fareControlCode, ROG]
-
A.
fareControl
Indicates that an entity is responsible for monitoring, enforcing, or managing payment of fares for access to a service or facility.
-
B.
fareControlUnifiedWith
Indicates that separate fare control areas are combined into a single, shared fare-controlled zone.
-
C.
fareControlLocation
Indicates a location where access to or use of a transportation service is regulated, checked, or controlled for fare payment.
-
D.
fareCodeLabel
Indicates the specific fare category or pricing code assigned to a ticket, expressed as a human-readable label.
-
E.
fareGroupCode
Indicates the code that identifies the fare group or category to which a particular fare or ticket belongs.
- F. None of above. chosen
Provenance (4 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_69f3499a59788190bff762a891471b31 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f7064d37388190993b2a7305a02b9f |
completed | May 3, 2026, 8:24 a.m. |
Created at: May 1, 2026, 1:49 a.m.