Triple
T31992138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 晏 |
E816899
|
entity |
| Predicate | readingInJapaneseOn |
P51401
|
FINISHED |
| Object | アン (an) |
—
|
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: アン (an) | Statement: [晏, readingInJapaneseOn, アン (an)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: readingInJapaneseOn Context triple: [晏, readingInJapaneseOn, アン (an)]
-
A.
japaneseOnReading
chosen
Indicates the on-yomi (Sino-Japanese) pronunciation associated with a given Japanese kanji or term.
-
B.
readingOf
Indicates that one entity is an interpretation, measurement, or recorded value derived from another entity.
-
C.
JapaneseNameReading
Indicates that one entity is the reading or pronunciation (e.g., in kana or romaji) of a Japanese name represented by the other entity.
-
D.
hasKanjiReading
Indicates that a written kanji character is associated with a specific reading or pronunciation.
-
E.
onYomiJapanese
Indicates that the specified reading is the on’yomi (Sino-Japanese) pronunciation associated with a given kanji or term.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b3b9ad2c8190ba59409cbd3da87f |
completed | May 3, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:13 a.m.