Triple
T22851697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 和人 |
E566370
|
entity |
| Predicate | 主要言語系統 |
P1252
|
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: [和人, 主要言語系統, 日本語族]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 主要言語系統 Context triple: [和人, 主要言語系統, 日本語族]
-
A.
hasWritingSystemForMajorLanguage
Indicates that there exists a writing system used to represent a major language associated with the given entity.
-
B.
languageOfPrimaryOutput
Indicates the language in which the primary output or main result of an entity (such as a work, process, or system) is expressed.
-
C.
primaryLanguageType
Indicates the main category or kind of language (such as spoken, written, or signed) that serves as the primary mode of communication in a given context or for a given entity.
-
D.
primaryLanguageOf
chosen
Indicates that a specified language is the main or official language used by a particular entity (such as a person, organization, or region).
-
E.
majorStandardLanguage
Indicates that a language is the primary or most widely used standard language associated with an entity (such as a country, region, or group).
- 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17eb9a5b8819091cbb4ac42fbf778 |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:36 p.m.