Triple
T30516089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khanke |
E776569
|
entity |
| Predicate | hasCampPopulation |
P195817
|
FINISHED |
| Object | Yazidi internally displaced persons |
—
|
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: Yazidi internally displaced persons | Statement: [Khanke, hasCampPopulation, Yazidi internally displaced persons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCampPopulation Context triple: [Khanke, hasCampPopulation, Yazidi internally displaced persons]
-
A.
hasPopulationOf
Indicates that an entity possesses a specific number of inhabitants or residents as its population.
-
B.
hasCurrentPopulationPlace
Indicates that a place currently has a specified population value or population-related attribute.
-
C.
hasPopulationApproximate
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
-
D.
hasPopulationStatus
Indicates the current demographic condition or classification of a population associated with an entity.
-
E.
hasServiceAreaPopulation
Indicates that an entity has a service area characterized by a specific population size or count.
- F. None of above. chosen
Provenance (4 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
| PDg | Predicate description generation | batch_69fde9fb68388190ada4a7018e2a2f76 |
completed | May 8, 2026, 1:49 p.m. |
Created at: April 29, 2026, 8:16 p.m.