Triple
T1877527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sundanese script |
E39177
|
entity |
| Predicate | UnicodeSupplementRange |
P1445
|
FINISHED |
| Object | U+1CC0–U+1CCF |
—
|
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: U+1CC0–U+1CCF | Statement: [Sundanese script, UnicodeSupplementRange, U+1CC0–U+1CCF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UnicodeSupplementRange Context triple: [Sundanese script, UnicodeSupplementRange, U+1CC0–U+1CCF]
-
A.
UnicodeBlock
chosen
Indicates that a character belongs to a specific contiguous range of code points defined as a Unicode block.
-
B.
printableCharacterRange
Indicates the range of characters that are considered printable within a given character set or encoding.
-
C.
basicMultilingualPlaneRange
Indicates that the referenced value or code point range lies within the Basic Multilingual Plane (BMP) of the Unicode character set.
-
D.
UnicodeStandardVersionIntroduced
Indicates the specific version of the Unicode Standard in which a given character, feature, or property was first introduced.
-
E.
UnicodeCodePointLowercase
Indicates that one Unicode code point is the lowercase mapping or lowercase equivalent of another code point.
- 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_69a8862f7074819096afe7fe65e179e9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb0f79fbc819085c54f3189a552d9 |
completed | March 7, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69abafe2b56c81909e13d543982e6e13 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.