Triple
T29584289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osman Yusuf Kenadid |
E753678
|
entity |
| Predicate | scriptDevised |
P53375
|
FINISHED |
| Object | Osmanya script |
—
|
NE NERFINISHED |
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: Osmanya script | Statement: [Osman Yusuf Kenadid, scriptDevised, Osmanya script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptDevised Context triple: [Osman Yusuf Kenadid, scriptDevised, Osmanya script]
-
A.
script
Indicates that an entity is associated with a written text or code (such as a screenplay, program, or written instructions) that defines its content or behavior.
-
B.
scriptEvolution
Indicates how a script or written system changes, develops, or transforms over time in relation to its earlier or later forms.
-
C.
scriptWriter
chosen
Indicates that one entity is the person who wrote or authored the script associated with another entity.
-
D.
scriptDirection
Indicates the direction in which a writing system or script is read or written (e.g., left-to-right, right-to-left, top-to-bottom).
-
E.
scripted
Indicates that one entity has written or created the script or dialogue for another entity or event.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 28, 2026, 6:09 p.m.