Triple
T29689215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 冯 |
E751169
|
entity |
| Predicate | hasJapaneseEquivalent |
P28734
|
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: [冯, hasJapaneseEquivalent, フウ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJapaneseEquivalent Context triple: [冯, hasJapaneseEquivalent, フウ]
-
A.
hasMeaningInJapanese
Indicates that something (such as a word, phrase, or symbol) possesses a specific meaning when interpreted in the Japanese language.
-
B.
hasNameInJapanese
chosen
Indicates that an entity is associated with a specific name expressed in the Japanese language.
-
C.
hasJapaneseText
Indicates that an entity contains or is associated with text written in the Japanese language.
-
D.
hasOfficialNameInJapanese
Indicates that an entity has an official, formally recognized name expressed in the Japanese language.
-
E.
japaneseVariant
Indicates that one entity is a Japanese-language or Japan-specific variant or version of another entity.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 7:15 p.m.