Triple
T29263485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kangxi Dictionary |
E741912
|
entity |
| Predicate | usesRadicalsForIndexing |
P170738
|
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: [Kangxi Dictionary, usesRadicalsForIndexing, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRadicalsForIndexing Context triple: [Kangxi Dictionary, usesRadicalsForIndexing, true]
-
A.
hasRadicalForm
Indicates that an entity (such as a character, symbol, or expression) possesses or is associated with a specific radical-based structural form.
-
B.
hasRadicalType
Indicates that an entity is associated with or classified by a specific type of radical (e.g., chemical, linguistic, or structural radical).
-
C.
belongsToRadical
Indicates that something is a component, member, or part of a specified radical group or radical element.
-
D.
usesKatakanaFor
Indicates that one entity is written or represented using katakana script in relation to another entity.
-
E.
usesHanjaVariants
Indicates that one entity employs or incorporates alternative Hanja (Chinese character) forms corresponding to another entity.
- 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 28, 2026, 12:43 p.m.