Triple
T23624882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenosha station |
E583434
|
entity |
| Predicate | lineEndpointRole |
P390
|
FINISHED |
| Object | northern terminus |
—
|
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: northern terminus | Statement: [Kenosha station, lineEndpointRole, northern terminus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineEndpointRole Context triple: [Kenosha station, lineEndpointRole, northern terminus]
-
A.
endPoint
chosen
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
-
B.
line6Terminus
Indicates the station or location where transit line 6 ends its route or service.
-
C.
hasDirectionEndpoints
Indicates that a directional element is defined or bounded by specific start and end points.
-
D.
secondaryEndpoint
Indicates that something serves as an additional, non-primary endpoint or target associated with a main endpoint in a relationship or process.
-
E.
endpointOnLake
Indicates that one end of a linear feature (such as a road, path, or boundary) terminates at or directly on the shore of a lake.
- 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b17c993c8190bf9ee3201869d240 |
completed | April 29, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:46 p.m.