Triple
T22110207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CJK Unified Ideographs Extension C |
E546391
|
entity |
| Predicate | assignedInSupplementaryArea |
P132522
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [CJK Unified Ideographs Extension C, assignedInSupplementaryArea, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assignedInSupplementaryArea Context triple: [CJK Unified Ideographs Extension C, assignedInSupplementaryArea, true]
-
A.
assignedToArea
Indicates that something has been allocated or designated to a specific area or region.
-
B.
isSupplementaryArea
chosen
Indicates that one area serves as an additional or supporting area to another primary area within a given context.
-
C.
assignedUnder
Indicates that one entity has been given responsibility, duty, or authority to act within the scope, supervision, or framework defined by another entity.
-
D.
assignedInStandard
Indicates that something is allocated or designated within a defined standard, specification, or normative framework.
-
E.
allottedTo
Indicates that something has been assigned or allocated to a particular entity as its designated recipient or user.
- 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_69e11e378dc08190896d6a51597afd5a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12948c2ec819083340787b2062649 |
completed | April 28, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:30 p.m.