Triple
T10265191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nguzo Saba |
E240694
|
entity |
| Predicate | corePrincipleMeaning_Kujichagulia |
P93011
|
FINISHED |
| Object | Self-Determination |
—
|
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: Self-Determination | Statement: [Nguzo Saba, corePrincipleMeaning_Kujichagulia, Self-Determination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: corePrincipleMeaning_Kujichagulia Context triple: [Nguzo Saba, corePrincipleMeaning_Kujichagulia, Self-Determination]
-
A.
typicalKanjiMeaning
Indicates that one entity is the standard or commonly accepted meaning associated with a given kanji character.
-
B.
japaneseKunReading
Indicates that a Japanese kanji character has a specific native Japanese (kun) reading associated with it.
-
C.
kanji
Indicates that an entity is written in, represented by, or associated with a specific kanji character or set of kanji characters.
-
D.
kun’yomiDerivedFrom
Indicates that a Japanese kun’yomi (native Japanese reading of a kanji) originates from or is historically derived from another form, source, or expression.
-
E.
componentKanji2
Indicates that one kanji character serves as the second component or sub-part of another kanji.
- F. None of above. chosen
Provenance (4 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_69d381a94c1881908fc38fc263d9b9c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2872830819080fdfa816167d04c |
completed | April 7, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ef6e6c81908a8ee52e4d28127b |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d285812c8190ab910dc85c53eebf |
completed | April 7, 2026, 9:46 a.m. |
Created at: April 6, 2026, 11:33 a.m.