Triple
T34888499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montreal–Quebec City |
E1006216
|
entity |
| Predicate | connectsLargestCityOfProvince |
P94566
|
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, connectsLargestCityOfProvince, Montreal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsLargestCityOfProvince Context triple: [Montreal–Quebec City, connectsLargestCityOfProvince, Montreal]
-
A.
capitalCityConnected
Indicates that there is a transportation or infrastructural link between a capital city and another location.
-
B.
connectsLargestCitiesOf
chosen
Indicates a relationship where something (typically a route, network, or infrastructure) links together the largest cities within a specified region or set.
-
C.
largestCity
Indicates that one city is the most populous or significant urban center within a specified region or entity.
-
D.
provinceCapitalOfProvince
Indicates that one entity is the capital city of a specified province.
-
E.
mainCityInTerritory
Indicates that a city serves as the primary or most important urban center within a specified territory.
- 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_69ff7595c9bc8190982c6e6e07a0c78f |
completed | May 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69ff715432a88190a25670d26614bde2 |
completed | May 9, 2026, 5:39 p.m. |
Created at: May 3, 2026, 4 p.m.