Triple
T8224291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMT lines |
E192138
|
entity |
| Predicate | fareControlChange |
P54837
|
FINISHED |
| Object | brought under city ownership in 1940 |
—
|
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: brought under city ownership in 1940 | Statement: [BMT lines, fareControlChange, brought under city ownership in 1940]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareControlChange Context triple: [BMT lines, fareControlChange, brought under city ownership in 1940]
-
A.
fareSystemChange
chosen
Indicates a change in the rules, structure, or method by which fares are calculated, collected, or applied.
-
B.
fareControl
Indicates that an entity is responsible for monitoring, enforcing, or managing payment of fares for access to a service or facility.
-
C.
fareControlUnifiedWith
Indicates that separate fare control areas are combined into a single, shared fare-controlled zone.
-
D.
fareFlexibility
Indicates how easily a fare can be changed, canceled, or refunded, and under what conditions or penalties.
-
E.
fareControlLocation
Indicates a location where access to or use of a transportation service is regulated, checked, or controlled for fare payment.
- 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_69ca82c9a8ac81908b011c38698456e4 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb77cc351481908d7dcd6d3d15d59f |
completed | March 31, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69cb36af41e081909dee92b9bc4947f1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:45 p.m.