Triple
T14231852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kawi |
E352768
|
entity |
| Predicate | inUnicodeGeneralCategory |
P26444
|
FINISHED |
| Object | Other Letter |
—
|
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: Other Letter | Statement: [Kawi, inUnicodeGeneralCategory, Other Letter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUnicodeGeneralCategory Context triple: [Kawi, inUnicodeGeneralCategory, Other Letter]
-
A.
UnicodePlane
Indicates that a Unicode code point belongs to a specific Unicode plane (a contiguous range of code points grouped by plane number).
-
B.
UnicodeBlock
Indicates that a character belongs to a specific contiguous range of code points defined as a Unicode block.
-
C.
UnicodeBlockName
Indicates the specific Unicode block to which a given character or code point belongs.
-
D.
UnicodeCodePointStandard
Indicates that a Unicode code point conforms to, or is defined within, a particular Unicode standard or version.
-
E.
hasUnicodeProperty
chosen
Indicates that an entity possesses a specific Unicode character property or set of properties (such as category, script, or other Unicode-defined attributes).
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de622cdd6481908befa179a9675bb5 |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:07 a.m.