Triple
T6096366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grantha (Unicode block) |
E135887
|
entity |
| Predicate | unicodeRangeStart |
P68100
|
FINISHED |
| Object | U+11300 |
—
|
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+11300 | Statement: [Grantha (Unicode block), unicodeRangeStart, U+11300]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unicodeRangeStart Context triple: [Grantha (Unicode block), unicodeRangeStart, U+11300]
-
A.
UnicodeBlock
Indicates that a character belongs to a specific contiguous range of code points defined as a Unicode block.
-
B.
unicodeCodePoint
Indicates that a character or symbol is associated with a specific Unicode code point value in the Unicode standard.
-
C.
printableCharacterRange
Indicates the range of characters that are considered printable within a given character set or encoding.
-
D.
basicMultilingualPlaneRange
Indicates that the referenced value or code point range lies within the Basic Multilingual Plane (BMP) of the Unicode character set.
-
E.
UnicodeCodePointStandard
Indicates that a Unicode code point conforms to, or is defined within, a particular Unicode standard or version.
- 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_69c0087cd3c48190b459848c72d84eb1 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05a9764048190ad4e9a02f9a25ab6 |
completed | March 22, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c049f5ac988190b62ba565153aaa35 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8e3f2c8190be459ca02f9b315a |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:12 p.m.