Triple
T6120381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nyanja |
E136466
|
entity |
| Predicate | hasAlphabetBasedOn |
P7160
|
FINISHED |
| Object | Latin alphabet |
—
|
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: Latin alphabet | Statement: [Nyanja, hasAlphabetBasedOn, Latin alphabet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlphabetBasedOn Context triple: [Nyanja, hasAlphabetBasedOn, Latin alphabet]
-
A.
usesAlphabet
chosen
Indicates that one entity employs or is written using the alphabet or writing system associated with another entity.
-
B.
hasBasicLetters
Indicates that an entity contains or is composed of fundamental alphabetic characters, without additional symbols or diacritics.
-
C.
usesLatinAlphabetSince
Indicates that an entity has employed the Latin alphabet as its writing system starting from a specific point in time and continuing thereafter.
-
D.
usesAlphabetResources
Indicates that an entity makes use of alphabet-related resources (such as letters, character sets, or alphabet-based tools) in performing an action or function.
-
E.
hasCyrillicAlphabetForm
Indicates that an entity has a corresponding representation or form written in the Cyrillic alphabet.
- 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_69c0089f851c81909e5e189a617dcff6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05bef8dc08190b917ad7209188c62 |
completed | March 22, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69c049f9ab3c81909c8ab6466f6a2935 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:14 p.m.