Triple
T34443206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flamborough, Ontario |
E884150
|
entity |
| Predicate | governmentTypeBeforeAmalgamation |
P40671
|
FINISHED |
| Object | 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: town | Statement: [Flamborough, Ontario, governmentTypeBeforeAmalgamation, town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentTypeBeforeAmalgamation Context triple: [Flamborough, Ontario, governmentTypeBeforeAmalgamation, town]
-
A.
governmentTypeBefore
chosen
Indicates the form of government that existed for an entity prior to a specified change or later government type.
-
B.
formerMunicipalityType
Indicates that an entity was previously classified as a specific type of municipality but no longer holds that municipal status.
-
C.
governmentType
Indicates the form or system of governance under which an entity (such as a country or organization) is organized and ruled.
-
D.
governingBodyPreviouslyKnownAs
Indicates that the governing body currently associated with an entity was formerly known by a different name.
-
E.
laterGovernmentType
Indicates that one government type succeeds or replaces another at a later point in time.
- 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a012594c27081908c80f0e0e6010290 |
completed | May 11, 2026, 12:40 a.m. |
| PD | Predicate disambiguation | batch_6a01252350548190b1df9edc9e581e91 |
completed | May 11, 2026, 12:38 a.m. |
Created at: May 1, 2026, 2 a.m.