Triple
T37479426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ko |
E931374
|
entity |
| Predicate | hasTypicalKanji |
P78040
|
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: [Ko, hasTypicalKanji, 子]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalKanji Context triple: [Ko, hasTypicalKanji, 子]
-
A.
hasKanjiReading
Indicates that a written kanji character is associated with a specific reading or pronunciation.
-
B.
hasNameInKanji
Indicates that an entity is associated with a specific written form of its name in Kanji characters.
-
C.
hasTraditionalCharacter
Indicates that an entity is associated with or represented by a traditional (non-simplified or historically established) written character form.
-
D.
typicalKanjiSpelling
chosen
Indicates that one written form is the standard or most commonly used kanji spelling for another expression (such as a word or phrase).
-
E.
kanji
Indicates that an entity is written in, represented by, or associated with a specific kanji character or set of kanji characters.
- 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_69f76ec382248190b47844df596123c6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffdf47d9608190830ca23d9cef6409 |
completed | May 10, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69ffdf00e2b4819082dd5cb78f316baf |
completed | May 10, 2026, 1:27 a.m. |
Created at: May 3, 2026, 4:17 p.m.