Triple
T6668592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chenoua |
E151666
|
entity |
| Predicate | spokenByPopulationStatus |
P9067
|
FINISHED |
| Object | small speech community |
—
|
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 speech community | Statement: [Chenoua, spokenByPopulationStatus, small speech community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spokenByPopulationStatus Context triple: [Chenoua, spokenByPopulationStatus, small speech community]
-
A.
hasPopulationStatus
chosen
Indicates the current demographic condition or classification of a population associated with an entity.
-
B.
haveSpeakerPopulation
Indicates that an entity has a specified number or population size of people who speak a particular language.
-
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.
usedByPopulation
Indicates that something is utilized or consumed by a specific population or group of people.
-
E.
supportedPopulation
Indicates that one entity provides assistance, resources, or services to sustain or benefit a specified group of people.
- 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_69c687f71fc081909dbd45d6377f6045 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce738fe88190a5557900efeec7ec |
completed | March 27, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69c6ad09974c81908784300ae218961f |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:02 p.m.