Triple
T34615911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danish regions |
E888862
|
entity |
| Predicate | numberOfMunicipalitiesWithin |
P30910
|
FINISHED |
| Object | 98 |
—
|
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: 98 | Statement: [Danish regions, numberOfMunicipalitiesWithin, 98]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfMunicipalitiesWithin Context triple: [Danish regions, numberOfMunicipalitiesWithin, 98]
-
A.
hasNumberOfMunicipalities
chosen
Indicates the relationship that specifies how many municipalities are associated with or contained within a given administrative or geographic entity.
-
B.
hasNumberOfMukims
Indicates the relationship specifying how many mukims (sub-district units) are associated with a given entity.
-
C.
hasMunicipalPart
Indicates that an administrative or territorial entity includes a municipality as one of its constituent parts.
-
D.
hasNumberOfSubdistricts
Indicates the relationship specifying how many subdistricts are associated with a given entity.
-
E.
isMunicipalFormationOf
Indicates that one administrative unit is formally established and recognized as the municipal formation corresponding to another territorial or administrative 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:03 a.m.