Triple
T23536313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laval Rocket |
E576708
|
entity |
| Predicate | cityInMetropolitanArea |
P42426
|
FINISHED |
| Object | Greater 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: Greater Montreal | Statement: [Laval Rocket, cityInMetropolitanArea, Greater Montreal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityInMetropolitanArea Context triple: [Laval Rocket, cityInMetropolitanArea, Greater Montreal]
-
A.
metropolitanOf
Indicates that one place serves as the primary metropolitan center or core urban area for another place or region.
-
B.
isMetropolitanOf
Indicates that one entity is the primary metropolitan area or major urban center associated with another entity, such as a region, country, or administrative division.
-
C.
metropolitanAreaWith
chosen
Indicates that one entity is a metropolitan area that includes, is associated with, or encompasses the other entity.
-
D.
homeCityMetropolitanArea
Indicates that a specified city serves as the primary metropolitan area associated with a given entity’s home location.
-
E.
cityIs
Indicates that one entity is a city associated with, or identified as, another entity.
- 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ae1738bc81909a7b761ddbaa1883 |
completed | April 29, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:10 p.m.