Triple
T25516772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston (via Lake Shore Limited) |
E639527
|
entity |
| Predicate | routeEndpointRole |
P100711
|
FINISHED |
| Object | eastern terminus city |
—
|
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: eastern terminus city | Statement: [Boston (via Lake Shore Limited), routeEndpointRole, eastern terminus city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeEndpointRole Context triple: [Boston (via Lake Shore Limited), routeEndpointRole, eastern terminus city]
-
A.
routeRole
Indicates the specific functional role or purpose that an entity has within a particular route or path.
-
B.
roleInGateway
Indicates that an entity holds a specific function or responsibility within a particular gateway system or process.
-
C.
roleInPath
chosen
Indicates that an entity participates in a specific path or route by occupying a particular role or position within that path.
-
D.
slaveRouteEndpoint
Indicates that a location serves as either the origin or destination point of a slave trade route.
-
E.
routeTypeAccessed
Indicates that a particular type of route has been accessed or used in some context.
- 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_69f5f832d48c8190984c9370816aaf94 |
completed | May 2, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 2:56 p.m.