Triple

T37000738
Position Surface form Disambiguated ID Type / Status
Subject Hamilton, Upper Canada E915339 entity
Predicate statusInProvince P33417 FINISHED
Object important regional market town 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: important regional market town | Statement: [Hamilton, Upper Canada, statusInProvince, important regional market town]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: statusInProvince
Context triple: [Hamilton, Upper Canada, statusInProvince, important regional market town]
  • A. hasProvinceStatus
    Indicates that an entity holds the administrative or political status of a province within a larger territorial or governmental system.
  • B. statusInRegion chosen
    Indicates the specific status or condition an entity holds within a particular geographic or administrative region.
  • C. regionStatus
    Indicates the current condition, classification, or operational state assigned to a specific geographic or administrative region.
  • D. statusProgramRegion
    Indicates the current state or condition of a program within a specific geographic or administrative region.
  • E. stationedInProvince
    Indicates that an entity is assigned or based in a particular province as its location or area of operation.
  • 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_69f76e8f1a8c81909db172ed31304971 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69ffc083a54c8190ac80d05ee8d20a6b completed May 9, 2026, 11:17 p.m.
PD Predicate disambiguation batch_69ffbfeb05b88190b4d50ce8124004d9 completed May 9, 2026, 11:14 p.m.
Created at: May 3, 2026, 4:14 p.m.