Triple
T1209402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 10646 |
E25964
|
entity |
| Predicate | maximumCodePoints |
P24670
|
FINISHED |
| Object | 1114112 |
—
|
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: 1114112 | Statement: [ISO/IEC 10646, maximumCodePoints, 1114112]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumCodePoints Context triple: [ISO/IEC 10646, maximumCodePoints, 1114112]
-
A.
hasCombiningMarks
Indicates that an entity (such as a character or string) includes one or more combining marks attached to a base element.
-
B.
basicMultilingualPlaneRange
Indicates that the referenced value or code point range lies within the Basic Multilingual Plane (BMP) of the Unicode character set.
-
C.
hasUnicode
Indicates that an entity is associated with, represented by, or encoded using a specific Unicode character or sequence.
-
D.
maximumSegmentLength
Indicates the greatest allowable or observed length of a segment within a given context or structure.
-
E.
UnicodeBlock
Indicates that a character belongs to a specific contiguous range of code points defined as a Unicode block.
- 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_69a4942b30f08190a91c60573e16b5ef |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bde30ce08190ab60a181ad2d321d |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6078088190ba0221ae3368416c |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bbf83584819088c69366f58586cc |
completed | March 1, 2026, 10:21 p.m. |
Created at: March 1, 2026, 7:46 p.m.