Triple
T6442055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supplementary Private Use Area-A |
E138247
|
entity |
| Predicate | lastCodePoint |
P44432
|
FINISHED |
| Object | 1048575 |
—
|
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: 1048575 | Statement: [Supplementary Private Use Area-A, lastCodePoint, 1048575]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastCodePoint Context triple: [Supplementary Private Use Area-A, lastCodePoint, 1048575]
-
A.
UnicodeCodePointFinal
chosen
Indicates that one entity is the final (last) Unicode code point in a specified sequence or representation associated with another entity.
-
B.
lastPrintableCharacter
Indicates that one character is the final non-whitespace (or otherwise displayable) character in a given sequence or string.
-
C.
hasUnicodeCodePoint
Indicates that a character or symbol is associated with a specific numeric Unicode code point value.
-
D.
DELCodePoint
Indicates a relationship where a specific code point corresponds to or is designated as the delete (DEL) control character in a character encoding system.
-
E.
unicodeCodePoint
Indicates that a character or symbol is associated with a specific Unicode code point value in the Unicode standard.
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06989dfb88190b25ff8b2c53f3ced |
completed | March 22, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69c060faaf248190bbdc8ff909c8777a |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:46 p.m.