Triple
T15241804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jackson (CTA Red Line station) |
E364272
|
entity |
| Predicate | isMajorChicagoLStation |
P106133
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Jackson (CTA Red Line station), isMajorChicagoLStation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorChicagoLStation Context triple: [Jackson (CTA Red Line station), isMajorChicagoLStation, yes]
-
A.
isMajorStationOn
Indicates that a station serves as a primary or significant stop on a particular route or line.
-
B.
chicagoTerminus
Indicates that a route, line, or service has its final terminus or endpoint in Chicago.
-
C.
isOneOfMajorStationsIn
chosen
Indicates that a station belongs to the set of primary or most important stations within a specified area or system.
-
D.
isMajorTransitPointFor
Indicates that a location serves as a primary hub or key node for the movement or transfer of people, goods, or vehicles within a transportation network.
-
E.
historicalChicagoTerminal
Indicates that an entity functioned as a historically significant terminal facility associated with Chicago.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007dcc33081908545ea1a1d2c19fe |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:13 a.m.