Triple
T7223648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N'Ko script |
E150322
|
entity |
| Predicate | unicodeScriptCode |
P11937
|
FINISHED |
| Object | Nko |
—
|
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: Nko | Statement: [N'Ko script, unicodeScriptCode, Nko]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unicodeScriptCode Context triple: [N'Ko script, unicodeScriptCode, Nko]
-
A.
unicodeCodePoint
Indicates that a character or symbol is associated with a specific Unicode code point value in the Unicode standard.
-
B.
hasUnicodeScript
Indicates that a character or text element belongs to a specific Unicode script category (such as Latin, Cyrillic, or Han).
-
C.
UnicodeCodePointStandard
Indicates that a Unicode code point conforms to, or is defined within, a particular Unicode standard or version.
-
D.
UnicodeBlock
Indicates that a character belongs to a specific contiguous range of code points defined as a Unicode block.
-
E.
scriptCodeISO15924
chosen
Indicates the script or writing system used to represent text, identified by its ISO 15924 code.
- 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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e9b54a5c8190a4a289f32853a8fe |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:54 p.m.