Triple
T29727250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lachen |
E752215
|
entity |
| Predicate | hasMunicipalCodeOfParent |
P3943
|
FINISHED |
| Object | 09181117 |
—
|
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: 09181117 | Statement: [Lachen, hasMunicipalCodeOfParent, 09181117]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMunicipalCodeOfParent Context triple: [Lachen, hasMunicipalCodeOfParent, 09181117]
-
A.
hasMunicipalityCode
chosen
Indicates that an entity is associated with a specific official municipality code used for administrative or identification purposes.
-
B.
postalCodeOfParentMunicipality
Indicates that an entity has the postal code associated with its parent municipality.
-
C.
hasParentCode
Indicates that an entity is associated with a parent code from which it is derived or to which it is hierarchically linked.
-
D.
hasMunicipalCodeCountry
Indicates that a municipal code is associated with, or belongs to, a specific country.
-
E.
hasMunicipalRelationshipWith
Indicates a formal or functional connection between two municipalities, such as cooperation, partnership, or administrative association.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 28, 2026, 7:40 p.m.