Triple
T2484520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chichewa |
E55892
|
entity |
| Predicate | hasSignificantSecondLanguageSpeakers |
P27353
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Chichewa, hasSignificantSecondLanguageSpeakers, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignificantSecondLanguageSpeakers Context triple: [Chichewa, hasSignificantSecondLanguageSpeakers, yes]
-
A.
secondLanguageSpeakers
chosen
Indicates that the referenced language is spoken as a second (non-native) language by the specified group or number of people.
-
B.
hasSecondaryLanguage
Indicates that an entity possesses or uses a secondary language in addition to its primary language.
-
C.
hasApproximateNativeSpeakers
Indicates that an entity is associated with an estimated or approximate number of people who speak it as their native language.
-
D.
hasSignificantLanguage
Indicates that an entity possesses a language that plays an important or primary role in its communication, identity, or functioning.
-
E.
isWidelySpokenIn
Indicates that a language is spoken by a large portion of the population across many regions or communities within a specified area.
- 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_69ab49e670a88190b928e08302381710 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd20b6d008190acec0eb172e218c9 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b7cf088190bcff4dac6150044c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.