Triple
T22050391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tertiary Ideographic Plane |
E544866
|
entity |
| Predicate | hexRange |
P132737
|
FINISHED |
| Object | 30000–3FFFF |
—
|
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: 30000–3FFFF | Statement: [Tertiary Ideographic Plane, hexRange, 30000–3FFFF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hexRange Context triple: [Tertiary Ideographic Plane, hexRange, 30000–3FFFF]
-
A.
hostRange
Indicates the range or set of different hosts that an organism, agent, or system can successfully inhabit, infect, or interact with.
-
B.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
C.
unicodeRangeHex
chosen
Indicates that a character or set of characters falls within a specified range of Unicode code points expressed in hexadecimal notation.
-
D.
testRange
Indicates that a value, condition, or behavior is being evaluated to determine whether it falls within a specified range or interval.
-
E.
zoneNumberRange
Indicates that there is an associated range of zone numbers, typically specifying the minimum and maximum zone identifiers applicable in a given 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128323fb08190b9592fd08a96cba0 |
completed | April 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:26 p.m.