Triple
T34888530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montreal–Quebec City |
E1006216
|
entity |
| Predicate | hasKeyRailStation |
P918
|
FINISHED |
| Object | Gare Centrale (Montreal) |
—
|
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: Gare Centrale (Montreal) | Statement: [Montreal–Quebec City, hasKeyRailStation, Gare Centrale (Montreal)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyRailStation Context triple: [Montreal–Quebec City, hasKeyRailStation, Gare Centrale (Montreal)]
-
A.
hasRailStation
Indicates that one entity possesses, contains, or is served by a rail station.
-
B.
hasRailwayStation
chosen
Indicates that a place or location is served by, or contains, a railway station.
-
C.
isRailwayStation
Indicates that the subject is a railway station, i.e., a facility where trains regularly stop to pick up or drop off passengers and/or freight.
-
D.
isKeyCommuterStation
Indicates that a station functions as a major hub for regular commuter traffic, serving as a primary access or transfer point for daily travelers.
-
E.
connectsToRailStation
Indicates that one entity has a direct link, route, or access connection to a rail station.
- 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 3, 2026, 4 p.m.