Triple
T25516811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York City (via Lake Shore Limited) |
E639528
|
entity |
| Predicate | westernConnectionCity |
P85889
|
FINISHED |
| Object | Chicago |
—
|
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: Chicago | Statement: [New York City (via Lake Shore Limited), westernConnectionCity, Chicago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: westernConnectionCity Context triple: [New York City (via Lake Shore Limited), westernConnectionCity, Chicago]
-
A.
connectsCityTo
Indicates a relationship in which a route, infrastructure, or link joins one city to another, enabling connection or interaction between them.
-
B.
connectsCity
Indicates a relationship where one entity serves as a link or route that joins or provides direct access between two cities.
-
C.
easternConnection
Indicates a relationship where one entity is connected to, aligned with, or positioned toward the east of another entity.
-
D.
primaryCityAtOtherEnd
chosen
Indicates that a given city is the main or principal city located at the opposite end of a specified route, connection, or relationship from another city.
-
E.
connectsSouthTo
Indicates that one entity is directly linked or joined to another entity located to its south.
- 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_69e75dbe32e48190a62d749a0ff2a96a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8339a8081908738ba23158091c9 |
completed | May 2, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:56 p.m.