Triple
T25101374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kumbo |
E628732
|
entity |
| Predicate | isSpokenLanguageRegion |
P141433
|
FINISHED |
| Object | Cameroonian Pidgin English |
—
|
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: Cameroonian Pidgin English | Statement: [Kumbo, isSpokenLanguageRegion, Cameroonian Pidgin English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSpokenLanguageRegion Context triple: [Kumbo, isSpokenLanguageRegion, Cameroonian Pidgin English]
-
A.
isSpokenLanguage
Indicates that a language is used primarily for oral communication by speakers, as opposed to being only written or symbolic.
-
B.
isSpokenOn
Indicates that a particular language, phrase, or utterance is used or occurs during a specified time, event, or occasion.
-
C.
alsoInLanguageRegion
Indicates that two or more entities are located within or associated with the same language-defined geographic region.
-
D.
isSpokenInAdministrativeUnit
chosen
Indicates that a particular language is used or officially spoken within a specified administrative unit or region.
-
E.
recognizedRegionalLanguage
Indicates that a language holds officially recognized status within a specific region or subnational jurisdiction.
- 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f464bd4d7081909fc0db6b8bf897b9 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:25 a.m.