Triple
T29840483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DE21L |
E757778
|
entity |
| Predicate | codeForTerritoryType |
P3820
|
FINISHED |
| Object | municipality |
—
|
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: municipality | Statement: [DE21L, codeForTerritoryType, municipality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeForTerritoryType Context triple: [DE21L, codeForTerritoryType, municipality]
-
A.
regionCodeType
chosen
Indicates the classification or format type used for a given region code within a coding or identification system.
-
B.
territoryCode
Indicates the standardized code assigned to a specific geographic or administrative territory in the relationship.
-
C.
codeForSovereignState
Indicates that an entity serves as a code or coded identifier that officially represents a particular sovereign state.
-
D.
regionCodeUsedIn
Indicates that a specific region code is utilized or applied within a particular context, system, or entity.
-
E.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67609bfcc81909df94d5e0a488c42 |
completed | May 2, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:39 p.m.