Triple
T15510862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kedzie |
E368703
|
entity |
| Predicate | isWithinNetworkZone |
P66218
|
FINISHED |
| Object | CTA standard fare zone |
—
|
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: CTA standard fare zone | Statement: [Kedzie, isWithinNetworkZone, CTA standard fare zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWithinNetworkZone Context triple: [Kedzie, isWithinNetworkZone, CTA standard fare zone]
-
A.
isOnNetwork
Indicates that an entity is currently connected to, accessible through, or operating within a specified network.
-
B.
inNetwork
chosen
Indicates that one entity is within the same defined network, system, or coverage group as another entity, such that network-based interactions or benefits apply between them.
-
C.
isInArea
Indicates that one entity is located within the spatial bounds or region defined by another entity.
-
D.
isInRemoteArea
Indicates that an entity is located in a geographically isolated or sparsely populated area, typically far from urban centers or standard infrastructure.
-
E.
inUniverseNetworkType
Indicates that one entity has a specific type or category of network within a particular fictional or defined universe in relation to another entity.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03fd008708190a3657863eb9ac626 |
completed | April 16, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:55 a.m.