Triple

T15026033
Position Surface form Disambiguated ID Type / Status
Subject Saint-Émile E378215 entity
Predicate nearbyNeighbourhood P4647 FINISHED
Object Loretteville E358871 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: Loretteville | Statement: [Saint-Émile, nearbyNeighbourhood, Loretteville]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Loretteville
Context triple: [Saint-Émile, nearbyNeighbourhood, Loretteville]
  • A. Loretteville chosen
    Loretteville is a residential district within Quebec City, Canada, known for its suburban character and local services.
  • B. Cloetesville
    Cloetesville is a residential suburb of Stellenbosch in South Africa’s Western Cape, historically developed as a predominantly Coloured community and now part of the greater Stellenbosch urban area.
  • C. Temperanceville
    Temperanceville is a small community within the Township of King in Ontario, Canada, known for its rural character and historic roots.
  • D. Westvale
    Westvale is a residential area in the town of Kirkby in Merseyside, England.
  • E. Lorneville
    Lorneville is a small community in Nova Scotia, Canada, located along the province’s northern shore near the New Brunswick border.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d85cd46b2c819090d054c27787f677 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded7dfcb508190aec8cd667e27a8ea completed April 15, 2026, 12:12 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe9dd746008190a7347368ee6d20cf completed May 9, 2026, 2:37 a.m.
Created at: April 10, 2026, 2:58 a.m.