Triple
T15422876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Japanese Language |
E369427
|
entity |
| Predicate | languageDiscussed |
P69046
|
FINISHED |
| Object | Japanese language |
—
|
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: Japanese language | Statement: [The Japanese Language, languageDiscussed, Japanese language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageDiscussed Context triple: [The Japanese Language, languageDiscussed, Japanese language]
-
A.
languageDiscussedIn
chosen
Indicates that a particular language is the topic of discussion within a specified context, source, or discourse.
-
B.
languageUse
Indicates the language or languages an entity uses for communication, expression, or interaction.
-
C.
languageCategory
Indicates the classification relationship where a language is assigned to a particular linguistic or functional category.
-
D.
languagesSpoken
Indicates that an entity is able to communicate using one or more specified languages.
-
E.
languageGroupSpoken
Indicates that a particular language group is spoken or used for communication by an 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ec032548190840b558dde6057c7 |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:20 a.m.