Triple
T21984971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eonmun |
E542933
|
entity |
| Predicate | characterComposition |
P91632
|
FINISHED |
| Object | syllabic blocks |
—
|
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: syllabic blocks | Statement: [Eonmun, characterComposition, syllabic blocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterComposition Context triple: [Eonmun, characterComposition, syllabic blocks]
-
A.
characterStructure
chosen
Indicates the structural or organizational relationship between a character and the components or elements that make up that character.
-
B.
characterCoverage
Indicates that one entity provides or includes sufficient representation or support for the characters (e.g., glyphs, symbols, or scripts) required or used by another entity.
-
C.
characterForm
Indicates that one entity is a particular form, version, or transformation state of a character.
-
D.
graphemeInventory
Indicates the set of distinct written symbols or characters used in a language or writing system.
-
E.
componentKanji2
Indicates that one kanji character serves as the second component or sub-part of another kanji.
- 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_69e0c48136b081908831fa907cc02e18 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12708cdcc81909511d9f81bd8f20e |
completed | April 28, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:04 p.m.