Triple
T14942135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pink Line at Clark/Lake |
E372555
|
entity |
| Predicate | farePaidAreaSharedWith |
P39868
|
FINISHED |
| Object | other elevated lines at Clark/Lake |
—
|
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: other elevated lines at Clark/Lake | Statement: [Pink Line at Clark/Lake, farePaidAreaSharedWith, other elevated lines at Clark/Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: farePaidAreaSharedWith Context triple: [Pink Line at Clark/Lake, farePaidAreaSharedWith, other elevated lines at Clark/Lake]
-
A.
hasFarePaidArea
chosen
Indicates that an entity includes or is associated with a zone where access is restricted to users who have paid a fare.
-
B.
fareZoneIncludes
Indicates that a specified fare zone geographically or logically contains a given location, stop, or segment for fare calculation purposes.
-
C.
feeArea
Indicates that access to or use of an area requires payment of a fee.
-
D.
fareIntegrationScope
Indicates the extent to which fares are coordinated or unified across different transportation services or systems.
-
E.
fareZoneUsage
Indicates how a fare zone is applied or utilized within a transportation or pricing context.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded68c1df0819084c0cd61b207d398 |
completed | April 15, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:38 a.m.