Triple

T28647670
Position Surface form Disambiguated ID Type / Status
Subject Cobden, Ontario E725105 entity
Predicate historicalNamingReason P112449 FINISHED
Object to honour free-trade advocate Richard Cobden LITERAL 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: to honour free-trade advocate Richard Cobden | Statement: [Cobden, Ontario, historicalNamingReason, to honour free-trade advocate Richard Cobden]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalNamingReason
Context triple: [Cobden, Ontario, historicalNamingReason, to honour free-trade advocate Richard Cobden]
  • A. historicalNameGivenBy
    Indicates that one entity is the name historically assigned to another entity by a specific source, culture, or period.
  • B. regionHistoricalName
    Indicates that a region has been known by a particular historical name during some past period.
  • C. historicMonikerReason chosen
    Indicates the reason or context for which a particular historic name or moniker was given to an entity.
  • D. historicallyNamedAfter
    Indicates that one entity received its name from another entity at some point in the past.
  • E. historicalNameType
    Indicates that the relationship specifies the type or category of a historical name associated with an 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_69f01d8423888190bd2f4e52605bf261 completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_69fe163a41a0819098403b470e327d29 completed May 8, 2026, 4:58 p.m.
PD Predicate disambiguation batch_69fe1358db5c819092570814a37ef5bd completed May 8, 2026, 4:46 p.m.
Created at: April 28, 2026, 4:49 a.m.