Triple
T15803290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 艾 |
E383147
|
entity |
| Predicate | hasRadical |
P78794
|
FINISHED |
| Object | 艹 |
—
|
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: 艹 | Statement: [艾, hasRadical, 艹]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRadical Context triple: [艾, hasRadical, 艹]
-
A.
semanticRadicalOfCharacter
chosen
Indicates that one element is the semantic radical (meaning-bearing component) of a given written character.
-
B.
kangxiRadicalName
Indicates the specific Kangxi radical name associated with a given Chinese character or radical index.
-
C.
kanji
Indicates that an entity is written in, represented by, or associated with a specific kanji character or set of kanji characters.
-
D.
hasTraditionalCharacter
Indicates that an entity is associated with or represented by a traditional (non-simplified or historically established) written character form.
-
E.
usesHanjaVariants
Indicates that one entity employs or incorporates alternative Hanja (Chinese character) forms corresponding to 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b524835c8190ae286b2562f07756 |
completed | April 16, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:48 a.m.