Triple
T5161184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salo |
E116439
|
entity |
| Predicate | municipalMergerYear |
P176
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Salo, municipalMergerYear, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalMergerYear Context triple: [Salo, municipalMergerYear, 2009]
-
A.
mergerYear
chosen
Indicates the year in which two or more entities formally merged into a single entity.
-
B.
unitaryAuthoritySince
Indicates the point in time from which an entity has held the status or role of a unitary authority.
-
C.
municipalityEstablished
Indicates that a municipality was officially created or founded at a specific point in time.
-
D.
formerMunicipalityOf
Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
-
E.
dateOfUnionFormation
Indicates the date on which a union was formally established or came into existence.
- 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_69bd445edb3881909b93b34d260717fc |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79073a54819080cd1e8de6fe906a |
completed | March 20, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69bd77b36c008190b91011a9fa52b3d2 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:44 p.m.