Triple
T37257587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umiken |
E924172
|
entity |
| Predicate | usedMunicipalCodeUntil |
P187348
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Umiken, usedMunicipalCodeUntil, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedMunicipalCodeUntil Context triple: [Umiken, usedMunicipalCodeUntil, 2019]
-
A.
municipalCodeSystem
Indicates a system that defines, organizes, or standardizes codes or regulations used by a municipality.
-
B.
usedToHaveMunicipalStatus
Indicates that an entity previously held municipal status (was officially recognized as a municipality) but no longer does.
-
C.
hasMunicipalityCode
Indicates that an entity is associated with a specific official municipality code used for administrative or identification purposes.
-
D.
hasMunicipalCodeJurisdiction
Indicates that an authority or entity holds official legal or regulatory power within a specific municipal code area or jurisdiction.
-
E.
hasMunicipalCodeAuthority
Indicates that an entity has the official power or jurisdiction to create, adopt, or enforce municipal codes, ordinances, or regulations.
- F. None of above. chosen
Provenance (4 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb4134225081909fd60703b8cae397 |
completed | May 6, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69fb35bf767081908de8345358ca7f44 |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb41333b548190912cb238ffc271c9 |
completed | May 6, 2026, 1:25 p.m. |
Created at: May 3, 2026, 4:15 p.m.