Triple
T7724176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ma |
E175086
|
entity |
| Predicate | semanticRadicalOfCharacter |
P78794
|
FINISHED |
| Object | horse radical |
—
|
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: horse radical | Statement: [Ma, semanticRadicalOfCharacter, horse radical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: semanticRadicalOfCharacter Context triple: [Ma, semanticRadicalOfCharacter, horse radical]
-
A.
kangxiRadicalName
Indicates the specific Kangxi radical name associated with a given Chinese character or radical index.
-
B.
kangxiRadicalNumber
Indicates the specific Kangxi radical index number associated with a given Chinese character or component.
-
C.
componentKanji2
Indicates that one kanji character serves as the second component or sub-part of another kanji.
-
D.
kanji
Indicates that an entity is written in, represented by, or associated with a specific kanji character or set of kanji characters.
-
E.
typicalKanjiMeaning
Indicates that one entity is the standard or commonly accepted meaning associated with a given kanji character.
- 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_69c6995d541c81909eaa646b1a8369a9 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7074eca4c8190bd51fd1b450729e8 |
completed | March 27, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69c7016a6cf88190b53bf4b958f0f302 |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c7074cd1f081908d5e8951660e7271 |
completed | March 27, 2026, 10:40 p.m. |
Created at: March 27, 2026, 4:05 p.m.