Triple
T24120224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fabre station |
E597632
|
entity |
| Predicate | locatedInAdministrativeBorough |
P300
|
FINISHED |
| Object | Rosemont–La Petite-Patrie |
E148049
|
NE 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: Rosemont–La Petite-Patrie | Statement: [Fabre station, locatedInAdministrativeBorough, Rosemont–La Petite-Patrie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInAdministrativeBorough Context triple: [Fabre station, locatedInAdministrativeBorough, Rosemont–La Petite-Patrie]
-
A.
locatedInBoroughCommunityDistrict
Indicates that something is situated within a specific borough community district.
-
B.
locatedInFormerBorough
Indicates that an entity is or was situated within the geographic area of a borough that no longer exists as an administrative unit.
-
C.
hasBorough
chosen
Indicates that one entity is located within, belongs to, or is administratively part of a specific borough.
-
D.
positionInBorough
Indicates that one entity is located within or belongs to the geographic area of a specific borough.
-
E.
isCentralBoroughOf
Indicates that a borough serves as the primary or central administrative or geographic district of a specified city or region.
- F. None of above.
Provenance (4 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_69e288c74200819098ab875b592cb39f |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dee2defc81909df55900769fef5b |
completed | April 29, 2026, 10:35 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a121e66e284819093df1feb202cd573 |
completed | May 23, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:05 p.m.