Triple
T418370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amish |
E8043
|
entity |
| Predicate | populationGrowthPattern |
P3837
|
FINISHED |
| Object | high birth rate |
—
|
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: high birth rate | Statement: [Amish, populationGrowthPattern, high birth rate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationGrowthPattern Context triple: [Amish, populationGrowthPattern, high birth rate]
-
A.
populationIncrease
chosen
Indicates that the number of individuals in a population has grown over a specified period of time.
-
B.
population
Indicates the total number of individuals living in or present within a specified area or group.
-
C.
populationClass
Indicates a categorical classification of a population based on shared characteristics, status, or demographic criteria.
-
D.
populationDensity
Indicates the number of individuals or entities occupying a unit area within a given region.
-
E.
hasPopulationType
Indicates that an entity’s population is classified according to a specific type or category (e.g., demographic, biological, or statistical grouping).
- 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eebde1d881908fb212bfba9d7c67 |
completed | Feb. 28, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69a2edd1ca148190a66bd8c5aad867d5 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.