Triple
T22701913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CJK Unified Ideographs extensions |
E561344
|
entity |
| Predicate | coversUsageDomain |
P1248
|
FINISHED |
| Object | historical texts |
—
|
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: historical texts | Statement: [CJK Unified Ideographs extensions, coversUsageDomain, historical texts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversUsageDomain Context triple: [CJK Unified Ideographs extensions, coversUsageDomain, historical texts]
-
A.
usedInDomain
chosen
Indicates that something (such as a concept, method, or resource) is applied or utilized within a particular domain or field.
-
B.
scopeOfUse
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
-
C.
eligibleUses
Indicates the types of actions, purposes, or contexts in which something is permitted or qualified to be used.
-
D.
endedUseWith
Indicates that an entity has stopped or terminated its use or association with another entity.
-
E.
isUsedUnder
Indicates that one entity is utilized or applied within the context, conditions, or framework defined by another entity.
- 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_69e2454e615481909c177440be559d2c |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178cb2f548190bfc6f050be7c795a |
completed | April 29, 2026, 3:19 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:15 p.m.