Triple
T2497427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zułów |
E52183
|
entity |
| Predicate | historicalPopulationType |
P6347
|
FINISHED |
| Object | rural settlement |
—
|
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: rural settlement | Statement: [Zułów, historicalPopulationType, rural settlement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPopulationType Context triple: [Zułów, historicalPopulationType, rural settlement]
-
A.
historicalMigrationType
Indicates the type or category of migration that occurred in a historical context between entities.
-
B.
hadPopulationType
chosen
Indicates that an entity possessed a particular classification or type of population during a given time or context.
-
C.
hasPopulationType
Indicates that an entity’s population is classified according to a specific type or category (e.g., demographic, biological, or statistical grouping).
-
D.
historicalPopulationMovement
Indicates the movement or migration of a population from one place to another during a specific historical period or event.
-
E.
formerPopulation
Indicates that an entity once had a certain population value or size during a past time period but no longer does.
- 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_69ab4955111c8190835bf619adec21ff |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd1ad2f8c81908853e97d75081e84 |
completed | March 7, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69abd0b980b481908d4932bcea4a6167 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.