Triple
T6060978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamato people |
E135030
|
entity |
| Predicate | ethnonymInJapanese |
P58738
|
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: [Yamato people, ethnonymInJapanese, 大和民族]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnonymInJapanese Context triple: [Yamato people, ethnonymInJapanese, 大和民族]
-
A.
ethnonymInLanguage
chosen
Indicates that a given term is the name used in a specified language to refer to the people of a particular ethnic group or nationality.
-
B.
eraNameInJapanese
Indicates the Japanese-language name used for a specific historical or calendar era.
-
C.
ethnonym
Indicates that one entity is the name of an ethnic group used to refer to the people associated with another entity.
-
D.
JapaneseNameOrigin
Indicates that one entity’s name originates from or is derived from the Japanese language or naming tradition in relation to another entity.
-
E.
ethnonymAttestedIn
Indicates that the name of an ethnic group (ethnonym) is documented or recorded in a specified source, context, or medium.
- 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_69c00878d06881909ee78e88913bf890 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0571fcecc8190a68e0d0668bbbfa7 |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049f031408190b08b2766237c5dd0 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:10 p.m.