Triple
T9343698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Habomai Islands |
E224826
|
entity |
| Predicate | languageUsedInClaims |
P41957
|
FINISHED |
| Object | 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: Japanese | Statement: [Habomai Islands, languageUsedInClaims, Japanese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageUsedInClaims Context triple: [Habomai Islands, languageUsedInClaims, Japanese]
-
A.
languageOfCoverage
Indicates the language in which the coverage, such as reporting or documentation about something, is expressed.
-
B.
claimsAboutLanguage
chosen
Indicates that one entity makes statements or assertions regarding the properties, use, status, or characteristics of a language.
-
C.
languageOfCommunications
Indicates that a specified language is used as the medium for communications associated with an entity or interaction.
-
D.
languageUsedAs
Indicates that one language is employed in a specific role, function, or context relative to another entity or situation.
-
E.
languageOfIssue
Indicates the language in which a particular item, document, or resource is issued or published.
- 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_69ca842993248190a79ab06968994b86 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4bb244e88190b269e0bc997f066a |
completed | April 1, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69cc7a66aef08190b8d668cff5b04f5f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:40 p.m.