Triple
T34888513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montreal–Quebec City |
E1006216
|
entity |
| Predicate | hasRoadTerminusCity |
P112663
|
FINISHED |
| Object | 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: Montreal | Statement: [Montreal–Quebec City, hasRoadTerminusCity, Montreal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadTerminusCity Context triple: [Montreal–Quebec City, hasRoadTerminusCity, Montreal]
-
A.
hasRoadTerminus
chosen
Indicates that one location or road segment serves as an endpoint or terminus for a particular road.
-
B.
hasMajorCityOnRoute
Indicates that a major city lies along, or is directly served by, a specified route or path between locations.
-
C.
terminusCityIsPort
Indicates that the city where a route or journey ends functions as a port.
-
D.
hasUrbanTerminus
Indicates that a route, line, or service ends or terminates within an urban area or city.
-
E.
roadTerminusOf
Indicates that a road ends at, or has its terminal point at, the referenced location or route.
- 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_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
Created at: May 3, 2026, 4 p.m.