Triple
T6442040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supplementary Private Use Area-A |
E138247
|
entity |
| Predicate | characterAssignmentPolicy |
P70652
|
FINISHED |
| Object | No characters assigned by Unicode |
—
|
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: No characters assigned by Unicode | Statement: [Supplementary Private Use Area-A, characterAssignmentPolicy, No characters assigned by Unicode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterAssignmentPolicy Context triple: [Supplementary Private Use Area-A, characterAssignmentPolicy, No characters assigned by Unicode]
-
A.
containsAssignedCharacters
Indicates that an entity includes or holds one or more characters that have been specifically assigned to it.
-
B.
ruleCharacterization
Indicates that one rule is described, defined, or characterized in terms of another rule or set of rules.
-
C.
characterFunction
Indicates the role, purpose, or narrative function that a character serves within a story or context.
-
D.
admissionPolicy
Indicates the rules or criteria governing whether and how entities are allowed to be admitted or granted access.
-
E.
characterCoverage
Indicates that one entity provides or includes sufficient representation or support for the characters (e.g., glyphs, symbols, or scripts) required or used by another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69c0623e3cd48190929b0e3cba013909 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:46 p.m.