Triple
T17465445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saluki |
E425263
|
entity |
| Predicate | connectsWithServiceAtChicago |
P127557
|
FINISHED |
| Object | Amtrak long-distance trains |
—
|
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: Amtrak long-distance trains | Statement: [Saluki, connectsWithServiceAtChicago, Amtrak long-distance trains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsWithServiceAtChicago Context triple: [Saluki, connectsWithServiceAtChicago, Amtrak long-distance trains]
-
A.
chicagoTerminus
Indicates that a route, line, or service has its final terminus or endpoint in Chicago.
-
B.
beganThroughServiceBetweenChicagoAndSouthBend
Indicates that an operation or activity was initiated by starting a service connecting Chicago and South Bend.
-
C.
communityAreaOfChicago
Indicates that a given entity is one of the officially designated community areas within the city of Chicago.
-
D.
connectsWithAirport
Indicates that there is a direct transportation or operational link established between an entity and an airport.
-
E.
connectsCityTo
Indicates a relationship in which a route, infrastructure, or link joins one city to another, enabling connection or interaction between them.
- 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.