Triple

T24481775
Position Surface form Disambiguated ID Type / Status
Subject Parc Saint-Viateur E617392 entity
Predicate locatedInMunicipalBorough P300 FINISHED
Object Outremont borough of 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: Outremont borough of Montreal | Statement: [Parc Saint-Viateur, locatedInMunicipalBorough, Outremont borough of Montreal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedInMunicipalBorough
Context triple: [Parc Saint-Viateur, locatedInMunicipalBorough, Outremont borough of Montreal]
  • A. hasMunicipalBorough
    Indicates that an administrative unit possesses or contains a specific municipal borough as part of its jurisdiction or structure.
  • B. hasBorough chosen
    Indicates that one entity is located within, belongs to, or is administratively part of a specific borough.
  • C. locatedInBoroughCommunityDistrict
    Indicates that something is situated within a specific borough community district.
  • D. boroughServed
    Indicates that a given entity (such as a facility, service, or route) serves or provides coverage to a specific borough.
  • E. locatedInFormerBorough
    Indicates that an entity is or was situated within the geographic area of a borough that no longer exists as an administrative unit.
  • 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_69e2d7f3ae788190b683394db15f220e completed April 18, 2026, 1:01 a.m.
NER Named-entity recognition batch_69f29ed6e1b08190b0a87d843b3cd8ae completed April 30, 2026, 12:14 a.m.
PD Predicate disambiguation batch_69f287d76c7c81909494f12e606a9149 completed April 29, 2026, 10:36 p.m.
Created at: April 18, 2026, 2:21 a.m.