Triple
T18459308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kripp |
E450988
|
entity |
| Predicate | parentMunicipalityHasPopulation |
P38055
|
FINISHED |
| Object | about 17000 |
—
|
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: about 17000 | Statement: [Kripp, parentMunicipalityHasPopulation, about 17000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentMunicipalityHasPopulation Context triple: [Kripp, parentMunicipalityHasPopulation, about 17000]
-
A.
municipalityPopulation
chosen
Indicates the total number of inhabitants living within a given municipality.
-
B.
isMostPopulousMunicipalityOf
Indicates that a municipality has the largest population among all municipalities within the specified administrative area or region.
-
C.
populationBasis
Indicates that a population measurement is based on, derived from, or defined with respect to a particular reference, criterion, or underlying basis.
-
D.
staffPopulationApprox
Indicates an approximate or estimated number of staff associated with an entity.
-
E.
isMunicipalHomeOf
Indicates that a municipality serves as the official home base or hosting location for a particular entity or organization.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52a7cdb5c8190a399f0e4052f7d1f |
completed | April 19, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:33 a.m.