Triple
T18563599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supplementary Multilingual Plane |
E453705
|
entity |
| Predicate | numericCodePointRangeEnd |
P9332
|
FINISHED |
| Object | 131071 |
—
|
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: 131071 | Statement: [Supplementary Multilingual Plane, numericCodePointRangeEnd, 131071]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numericCodePointRangeEnd Context triple: [Supplementary Multilingual Plane, numericCodePointRangeEnd, 131071]
-
A.
unicodeRangeStart
Indicates the starting code point in Unicode for a specified range of characters or symbols.
-
B.
maximumCodePoints
Indicates the maximum number of Unicode code points that are allowed or supported in a given context or value.
-
C.
UnicodeCodePointFinal
Indicates that one entity is the final (last) Unicode code point in a specified sequence or representation associated with another entity.
-
D.
rangeEnd
chosen
Indicates the endpoint or upper boundary value of a specified range in a relationship or measurement.
-
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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53afc57448190abd90167d7e12a18 |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:42 a.m.