Triple
T15510851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kedzie |
E368703
|
entity |
| Predicate | hasTicketBarrierLocation |
P107454
|
FINISHED |
| Object | station house at street level |
—
|
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: station house at street level | Statement: [Kedzie, hasTicketBarrierLocation, station house at street level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTicketBarrierLocation Context triple: [Kedzie, hasTicketBarrierLocation, station house at street level]
-
A.
hasTicketBarrier
Indicates that an access-controlled barrier or gate is present, typically requiring a valid ticket or pass to pass through.
-
B.
hasTicketGatesLocation
chosen
Indicates that a place or facility has ticket gates located at or within a specified location.
-
C.
hasTicketHall
Indicates that a place or facility includes or is equipped with a designated ticket hall area for purchasing or validating tickets.
-
D.
hasTicketInspection
Indicates that a ticket is checked or verified by an authorized inspector or system.
-
E.
hasTicketRequirement
Indicates that an entity is subject to a specific ticket or admission requirement in order for access, participation, or use to be allowed.
- 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.