Triple
T17787816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokara Islands |
E444064
|
entity |
| Predicate | localDialects |
P1762
|
FINISHED |
| Object | Ryukyuan-influenced dialects |
—
|
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: Ryukyuan-influenced dialects | Statement: [Tokara Islands, localDialects, Ryukyuan-influenced dialects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localDialects Context triple: [Tokara Islands, localDialects, Ryukyuan-influenced dialects]
-
A.
regionalDialect
chosen
Indicates that one entity uses or is associated with a dialect specific to a particular geographic region in relation to another entity.
-
B.
languageUsedInLocality
Indicates that a particular language is used or spoken within a specific locality or geographic area.
-
C.
majorDialectOf
Indicates that one dialect is the primary or most prominent dialect associated with a particular language or region.
-
D.
notableDialect
Indicates that an entity is recognized for having a distinct or noteworthy dialect associated with it.
-
E.
consideredDialectOf
Indicates that one language variety is regarded as a dialect of another language or linguistic standard.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48794542c8190b049bce6e28c9f3a |
completed | April 19, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:12 a.m.