Triple
T28495506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago–San Francisco corridor |
E721096
|
entity |
| Predicate | hasEndpointState |
P34947
|
FINISHED |
| Object | Illinois |
—
|
NE NERFINISHED |
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: Illinois | Statement: [Chicago–San Francisco corridor, hasEndpointState, Illinois]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndpointState Context triple: [Chicago–San Francisco corridor, hasEndpointState, Illinois]
-
A.
hasEndpointType
Indicates that an entity has a specific type or classification assigned to one of its endpoints.
-
B.
endPointState
Indicates the resulting condition or status that an entity or process is in at its termination or final point.
-
C.
hasPrimaryEndpoint
Indicates that an entity designates another entity as its main or most important endpoint or target location.
-
D.
hasEndpointStation
chosen
Indicates that something (such as a route, line, or service) has a specific station as one of its terminal endpoints.
-
E.
hasDestinationState
Indicates that an entity is associated with, directed toward, or results in a particular destination state or condition.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 28, 2026, 3:03 a.m.