Triple
T11568941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haileybury |
E274333
|
entity |
| Predicate | dateOfMunicipalAmalgamation |
P50534
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [Haileybury, dateOfMunicipalAmalgamation, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfMunicipalAmalgamation Context triple: [Haileybury, dateOfMunicipalAmalgamation, 2004]
-
A.
unitaryAuthoritySince
Indicates the point in time from which an entity has held the status or role of a unitary authority.
-
B.
dateOfUnionFormation
Indicates the date on which a union was formally established or came into existence.
-
C.
partOfMunicipalitySince
Indicates that an entity has been included within and administratively belonging to a specific municipality starting from a given point in time.
-
D.
annexationDate
Indicates the date on which one entity formally annexed or incorporated another entity into its territory or jurisdiction.
-
E.
incorporatedIntoOnDate
chosen
Indicates that one entity was formally incorporated into or merged with another entity on a specific date.
- 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88dd543a48190b834abd8e8ae7b65 |
completed | April 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69d85dc3fc2c8190bed7e2111301a77c |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:37 p.m.