Triple
T25285766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Purépecha |
E633934
|
entity |
| Predicate | isSubclassificationOf |
P24573
|
FINISHED |
| Object | Purépecha 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: Purépecha dialects | Statement: [Western Purépecha, isSubclassificationOf, Purépecha dialects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSubclassificationOf Context triple: [Western Purépecha, isSubclassificationOf, Purépecha dialects]
-
A.
subclassOf
Indicates that one class is a more specific type of another class, inheriting its characteristics as a subset of it.
-
B.
isClassifiedUnder
chosen
Indicates that one entity is categorized or grouped within a broader class, type, or category represented by another entity.
-
C.
subbranchOf
Indicates that one entity is a subordinate or secondary branch derived from, and structurally dependent on, another entity.
-
D.
subclassificationStatus
Indicates the classification state or category assigned to a subclass within a broader classification system.
-
E.
basisOfClassification
Indicates that one entity serves as the criterion or foundation used to classify or categorize another 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 1:19 p.m.