Triple
T23387514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PUA-A |
E593923
|
entity |
| Predicate | hasRangeSize |
P26442
|
FINISHED |
| Object | 65536 code points |
—
|
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: 65536 code points | Statement: [PUA-A, hasRangeSize, 65536 code points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRangeSize Context triple: [PUA-A, hasRangeSize, 65536 code points]
-
A.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
B.
rangeSize
chosen
Indicates the extent or magnitude of the range over which something applies, varies, or is distributed.
-
C.
hasLengthRange
Indicates that an entity’s length falls within a specified minimum-to-maximum range.
-
D.
includesSizeRange
Indicates that one entity specifies or covers a particular range of sizes associated with another entity.
-
E.
hasRangeCategory
Indicates that a property or measurement falls within a specified category or interval of possible values.
- 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a498fd08819085e90a872d9d0c7a |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:35 p.m.