Triple
T30447196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yi Radicals |
E774610
|
entity |
| Predicate | hasRadicalsFor |
P170738
|
FINISHED |
| Object | Yi dictionaries |
—
|
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: Yi dictionaries | Statement: [Yi Radicals, hasRadicalsFor, Yi dictionaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRadicalsFor Context triple: [Yi Radicals, hasRadicalsFor, Yi dictionaries]
-
A.
hasRadicalType
Indicates that an entity is associated with or classified by a specific type of radical (e.g., chemical, linguistic, or structural radical).
-
B.
hasRadicalForm
Indicates that an entity (such as a character, symbol, or expression) possesses or is associated with a specific radical-based structural form.
-
C.
usesRadicalsForIndexing
chosen
Indicates that something organizes or looks up written characters based on their constituent radicals as the primary indexing method.
-
D.
belongsToRadical
Indicates that something is a component, member, or part of a specified radical group or radical element.
-
E.
semanticRadicalOfCharacter
Indicates that one element is the semantic radical (meaning-bearing component) of a given written character.
- 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 29, 2026, 8:09 p.m.