Triple
T3183310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gosford |
E66640
|
entity |
| Predicate | localGovernmentAmalgamationYear |
P9024
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Gosford, localGovernmentAmalgamationYear, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localGovernmentAmalgamationYear Context triple: [Gosford, localGovernmentAmalgamationYear, 2016]
-
A.
municipalityEstablished
Indicates that a municipality was officially created or founded at a specific point in time.
-
B.
reunifiedAsCapitalInYear
Indicates that an entity regained its status as a capital city in a specified year after a period of not holding that status.
-
C.
formerMunicipalityOf
Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
-
D.
dateOfUnionFormation
Indicates the date on which a union was formally established or came into existence.
-
E.
annexationDate
chosen
Indicates the date on which one entity formally annexed or incorporated another entity into its territory or jurisdiction.
- 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_69ad8587c1bc8190a2595f2c22ee1001 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada6bea1788190bbce7cb52f8e72e8 |
completed | March 8, 2026, 4:41 p.m. |
| PD | Predicate disambiguation | batch_69ad9e02677c8190a21d93b1259b2761 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.