Triple
T16188511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Agaw |
E392871
|
entity |
| Predicate | hasMinoritySpeakersIn |
P4250
|
FINISHED |
| Object | Diaspora communities |
—
|
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: Diaspora communities | Statement: [North Agaw, hasMinoritySpeakersIn, Diaspora communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMinoritySpeakersIn Context triple: [North Agaw, hasMinoritySpeakersIn, Diaspora communities]
-
A.
isSpokenByMinority
Indicates that the language or dialect is used primarily by a numerically smaller or less dominant group within a larger population.
-
B.
spokenByMinorityIn
chosen
Indicates that a language or dialect is used primarily by a minority group within a specified geographic or political region.
-
C.
areMinorityLanguagesIn
Indicates that the subject languages are minority (non-dominant) languages within the specified region, country, or larger linguistic context.
-
D.
linguisticMinorityIn
Indicates that a group or population constitutes a linguistic minority within a specified geographic or political region.
-
E.
hasNativeSpeakers
Indicates that a language or dialect is spoken as a first language by one or more people or populations.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e222d3a8e48190bdf29a633f4b0490 |
completed | April 17, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.