Triple
T17465457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saluki |
E425263
|
entity |
| Predicate | routePurpose |
P127558
|
FINISHED |
| Object | connect Chicago with Southern Illinois |
—
|
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: connect Chicago with Southern Illinois | Statement: [Saluki, routePurpose, connect Chicago with Southern Illinois]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routePurpose Context triple: [Saluki, routePurpose, connect Chicago with Southern Illinois]
-
A.
routePlan
Indicates a planned path or sequence of steps for traveling from a starting point to a destination.
-
B.
routeDescription
Indicates a textual explanation or summary of the path, course, or itinerary taken between locations.
-
C.
journeyPurpose
Indicates the reason or intended goal motivating an entity’s journey or trip.
-
D.
routeVia
Indicates that a connection, path, or communication between two points is established or carried out through an intermediate location, node, or channel.
-
E.
routeCategory
Indicates the classification or type assigned to a route within a transportation or path network.
- F. None of above. chosen
Provenance (4 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451a6c2e08190bca9de56ee2f5136 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:47 a.m.