Triple
T15329733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cooma |
E366500
|
entity |
| Predicate | gazettedAsMunicipality |
P23872
|
FINISHED |
| Object | 1879 |
—
|
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: 1879 | Statement: [Cooma, gazettedAsMunicipality, 1879]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gazettedAsMunicipality Context triple: [Cooma, gazettedAsMunicipality, 1879]
-
A.
municipalityEstablished
chosen
Indicates that a municipality was officially created or founded at a specific point in time.
-
B.
incorporatedAsMunicipality
Indicates that an area or settlement has been legally established and recognized as a municipality through a formal incorporation process.
-
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.
hasMunicipalFormation
Indicates that an administrative or territorial unit is organized into, or associated with, a specific municipal formation as its local self-governing structure.
-
E.
establishedAsPrefecture
Indicates that an entity was formally designated or created as a prefecture at a specific 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e0161ac8190aa1d52c063c02ad0 |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:17 a.m.