Triple
T6441991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supplementary Special-purpose Plane |
E138246
|
entity |
| Predicate | lowestCodePoint |
P68100
|
FINISHED |
| Object | U+E0000 |
—
|
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+E0000 | Statement: [Supplementary Special-purpose Plane, lowestCodePoint, U+E0000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowestCodePoint Context triple: [Supplementary Special-purpose Plane, lowestCodePoint, U+E0000]
-
A.
UnicodeCodePointLowercase
Indicates that one Unicode code point is the lowercase mapping or lowercase equivalent of another code point.
-
B.
unicodeCodePoint
Indicates that a character or symbol is associated with a specific Unicode code point value in the Unicode standard.
-
C.
maximumCodePoints
Indicates the maximum number of Unicode code points that are allowed or supported in a given context or value.
-
D.
unicodeRangeStart
chosen
Indicates the starting code point in Unicode for a specified range of characters or symbols.
-
E.
lowestPoint
Indicates that one entity is the point with the minimum vertical position or value relative to another entity or within a specified context.
- 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_69c060f96980819091bab9335922a457 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:46 p.m.