Triple
T7030106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alevism |
E163246
|
entity |
| Predicate | populationEstimateRange |
P28398
|
FINISHED |
| Object | 10–25 million adherents |
—
|
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: 10–25 million adherents | Statement: [Alevism, populationEstimateRange, 10–25 million adherents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationEstimateRange Context triple: [Alevism, populationEstimateRange, 10–25 million adherents]
-
A.
populationRange
chosen
Indicates the numerical interval within which the size of a population falls.
-
B.
populationScale
Indicates the relative size or magnitude of a population, typically categorizing it into broad scale levels (e.g., small, medium, large).
-
C.
demographicScope
Indicates the specific population group or demographic segment to which something (e.g., a policy, study, product, or service) is targeted or applicable.
-
D.
hasPopulationApproximate
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
-
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_69c6885d691c81908cf7d31083113886 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e458ad9c81908c3f492b317ce291 |
completed | March 27, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b9a2488190aea351d96afa5a12 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:35 p.m.