Triple
T23449283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brong-Ahafo Region |
E567728
|
entity |
| Predicate | majorLocalLanguages |
P11430
|
FINISHED |
| Object | Twi |
—
|
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: Twi | Statement: [Brong-Ahafo Region, majorLocalLanguages, Twi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorLocalLanguages Context triple: [Brong-Ahafo Region, majorLocalLanguages, Twi]
-
A.
languageUsedInLocality
Indicates that a particular language is used or spoken within a specific locality or geographic area.
-
B.
typicalLanguages
Indicates the languages that are commonly or characteristically used, spoken, or associated with a given entity.
-
C.
ethnicLanguageStatus
Indicates the status or role of a language in relation to a particular ethnic group (e.g., primary, secondary, heritage, or minority language).
-
D.
regionLanguage
Indicates that a particular language is used or officially recognized within a specific geographic region.
-
E.
majorityLanguageOf
chosen
Indicates that a given language is the primary or most widely spoken language within a specified group, region, or entity.
- 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_69e2458b4c888190b1d7998f9862a558 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a64c1ee081908ba3adf5ce80d6a5 |
completed | April 29, 2026, 6:33 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:52 p.m.