Triple
T20018112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halsa |
E494775
|
entity |
| Predicate | formerMunicipalityEstablished |
P23872
|
FINISHED |
| Object | 1838 |
—
|
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: 1838 | Statement: [Halsa, formerMunicipalityEstablished, 1838]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerMunicipalityEstablished Context triple: [Halsa, formerMunicipalityEstablished, 1838]
-
A.
municipalityEstablished
chosen
Indicates that a municipality was officially created or founded at a specific point in time.
-
B.
formerMunicipalityOf
Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
-
C.
formedMunicipalityOn
Indicates that a new municipality was officially created or established on a specific date.
-
D.
unitaryAuthoritySince
Indicates the point in time from which an entity has held the status or role of a unitary authority.
-
E.
wasFoundedAsTown
Indicates that an entity came into existence specifically with the legal or formal status of a town.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6623d76808190988990a8dc263ef7 |
completed | April 20, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:34 p.m.