Triple
T415040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Yamato |
E9573
|
entity |
| Predicate | languageTraditionallyUsed |
P8513
|
FINISHED |
| Object | Classical Japanese |
—
|
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: Classical Japanese | Statement: [House of Yamato, languageTraditionallyUsed, Classical Japanese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageTraditionallyUsed Context triple: [House of Yamato, languageTraditionallyUsed, Classical Japanese]
-
A.
languageOfExpression
chosen
Indicates that a particular language is used as the medium or form in which an expression (such as a text, utterance, or work) is realized.
-
B.
languageForm
Indicates the specific linguistic form or expression in which something is conveyed or represented.
-
C.
languagesSpoken
Indicates that an entity is able to communicate using one or more specified languages.
-
D.
regionLanguage
Indicates that a particular language is used or officially recognized within a specific geographic region.
-
E.
languageFamily
Indicates that two or more languages belong to the same genealogical language family or linguistic lineage.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eebde1d881908fb212bfba9d7c67 |
completed | Feb. 28, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69a2edcff4688190809d83d112ff25a5 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:09 p.m.