Triple
T33867420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington/Dearborn |
E868095
|
entity |
| Predicate | fareControlConnectionWith |
P83159
|
FINISHED |
| Object | Washington/State |
—
|
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: Washington/State | Statement: [Washington/Dearborn, fareControlConnectionWith, Washington/State]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareControlConnectionWith Context triple: [Washington/Dearborn, fareControlConnectionWith, Washington/State]
-
A.
fareControlUnifiedWith
Indicates that separate fare control areas are combined into a single, shared fare-controlled zone.
-
B.
fareControl
Indicates that an entity is responsible for monitoring, enforcing, or managing payment of fares for access to a service or facility.
-
C.
fareControlLocation
Indicates a location where access to or use of a transportation service is regulated, checked, or controlled for fare payment.
-
D.
fareControlLayout
Indicates how fare control elements (such as gates, turnstiles, or barriers) are arranged or organized within a transit or ticketing area.
-
E.
fareControlSeparatedFrom
chosen
Indicates that the fare-controlled (ticketed) area of one transit facility is physically separated from that of another, requiring passengers to exit and re-enter fare control to transfer between them.
- 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_69f34995029081909ede0f7df73d1a5e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f700a3bf1c819099666c5ad645eea2 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5a4f7881909324eb3c20ca96f1 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.