Triple
T1079877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UTF-32 |
E23921
|
entity |
| Predicate | doesNotEncode |
P4300
|
FINISHED |
| Object | noncharacters outside Unicode range |
—
|
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: noncharacters outside Unicode range | Statement: [UTF-32, doesNotEncode, noncharacters outside Unicode range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotEncode Context triple: [UTF-32, doesNotEncode, noncharacters outside Unicode range]
-
A.
doesNotProtect
Indicates that an entity fails to provide protection or safeguarding to another entity or object.
-
B.
doesNot
chosen
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
C.
doesNotUse
Indicates that one entity intentionally refrains from employing, utilizing, or relying on another entity, method, or resource.
-
D.
doesNotSpecify
Indicates that the subject intentionally leaves some information, detail, or attribute undefined or unspecified with respect to the object.
-
E.
doesNotStandFor
Indicates that one entity does not represent, symbolize, or act on behalf of another entity in any capacity.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b94509d08190964509ea4a2d7912 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73d9f08819093668104f129840e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.