Triple
T21518817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Einwohnergemeinde |
E530917
|
entity |
| Predicate | hasPopulationRegister |
P141158
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Einwohnergemeinde, hasPopulationRegister, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPopulationRegister Context triple: [Einwohnergemeinde, hasPopulationRegister, yes]
-
A.
hasRegisteredPopulation
chosen
Indicates that an entity has an officially recorded number of inhabitants in a population registry or census.
-
B.
hasResidentPopulation
Indicates that a place or administrative area has a population of people who live there permanently or for an extended period.
-
C.
hasPopulationStatus
Indicates the current demographic condition or classification of a population associated with an entity.
-
D.
nationalRegister
Indicates that an entity is officially listed in a country's national register, typically recognizing it for legal, historical, or administrative purposes.
-
E.
hasPopulationAsOf
Indicates that a population count is associated with a specific point or date in time when that population figure was valid or recorded.
- 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_69e0c45d95a081908e7962ad215da746 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee81438cbc8190aba0f546b27eb2a4 |
completed | April 26, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:25 p.m.