Triple
T6060823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amami language |
E135027
|
entity |
| Predicate | isOftenMisclassifiedAs |
P2289
|
FINISHED |
| Object | Japanese dialect |
—
|
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 dialect | Statement: [Amami language, isOftenMisclassifiedAs, Japanese dialect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOftenMisclassifiedAs Context triple: [Amami language, isOftenMisclassifiedAs, Japanese dialect]
-
A.
isSometimesClassifiedAs
Indicates that an entity is occasionally, but not consistently or universally, categorized under a particular type or class.
-
B.
misidentifiedAs
Indicates that one entity has been incorrectly recognized, labeled, or understood as another, distinct entity.
-
C.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
D.
isClassifiedUnder
Indicates that one entity is categorized or grouped within a broader class, type, or category represented by another entity.
-
E.
oftenConfusedWith
chosen
Indicates that one entity is frequently mistaken for or thought to be another due to similarity or ambiguity.
- 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_69c00878d06881909ee78e88913bf890 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0571fcecc8190a68e0d0668bbbfa7 |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049f031408190b08b2766237c5dd0 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:10 p.m.