Triple
T32185410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 勇武 |
E822094
|
entity |
| Predicate | kanjiMeaning武 |
P75329
|
FINISHED |
| Object | military might |
—
|
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: military might | Statement: [勇武, kanjiMeaning武, military might]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kanjiMeaning武 Context triple: [勇武, kanjiMeaning武, military might]
-
A.
componentKanji1Meaning
Indicates that the first kanji component of a character corresponds to a particular meaning or semantic value.
-
B.
typicalKanjiMeaning
chosen
Indicates that one entity is the standard or commonly accepted meaning associated with a given kanji character.
-
C.
possibleKanjiMeaning
Indicates that a given meaning is a possible or candidate interpretation associated with a particular kanji character.
-
D.
kanji
Indicates that an entity is written in, represented by, or associated with a specific kanji character or set of kanji characters.
-
E.
meaningOfKanji司
Indicates that one entity represents or explains the meaning or semantic content of the kanji 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bab9100c8190ad1f86fece0fc505 |
completed | May 3, 2026, 3:02 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:35 a.m.