Triple
T6343818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode Hebrew block |
E142695
|
entity |
| Predicate | hasUnicodeRangeEnd |
P9332
|
FINISHED |
| Object | U+05FF |
—
|
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+05FF | Statement: [Unicode Hebrew block, hasUnicodeRangeEnd, U+05FF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnicodeRangeEnd Context triple: [Unicode Hebrew block, hasUnicodeRangeEnd, U+05FF]
-
A.
unicodeRangeStart
Indicates the starting code point in Unicode for a specified range of characters or symbols.
-
B.
hasControlCharacterRange
Indicates that there exists a specified range of control characters associated with or applicable to an entity.
-
C.
hasUnicode
Indicates that an entity is associated with, represented by, or encoded using a specific Unicode character or sequence.
-
D.
hasBlockUnicode
Indicates that one entity possesses or is associated with a specific Unicode block related to another entity.
-
E.
rangeEnd
chosen
Indicates the endpoint or upper boundary value of a specified range in a relationship or measurement.
- 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_69c008d5ab108190b346c465696824a9 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0674702d08190806ef0998960b797 |
completed | March 22, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69c060ea1a988190889e47b7e0c819b8 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:31 p.m.