Triple
T16156935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nantouillet |
E392068
|
entity |
| Predicate | populationCentreType |
P11334
|
FINISHED |
| Object | small commune |
—
|
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: small commune | Statement: [Nantouillet, populationCentreType, small commune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationCentreType Context triple: [Nantouillet, populationCentreType, small commune]
-
A.
hasPopulationCenterType
chosen
Indicates the classification of a population center by its type, such as city, town, village, or other settlement category.
-
B.
hasPopulationCenter
Indicates that an area, region, or administrative unit contains or is served by a primary settlement or population hub.
-
C.
notablePopulationCenter
Indicates that a location is recognized as a significant or prominent center of population within a given area or context.
-
D.
majorPopulationCenter
Indicates that a location functions as a primary hub of population concentration and activity within a region.
-
E.
administrativeCentreType
Indicates the specific kind or level of administrative center that a place serves as within an administrative hierarchy.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21e5b57a48190b6fe21f1c63e1ba3 |
completed | April 17, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_69e1828abb608190a99d86bce1d77de2 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.