Triple
T25380591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Purépecha |
E631374
|
entity |
| Predicate | hasSuperordinateEntity |
P47433
|
FINISHED |
| Object | Purépecha language |
—
|
NE NERFINISHED |
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 language | Statement: [Central Purépecha, hasSuperordinateEntity, Purépecha language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuperordinateEntity Context triple: [Central Purépecha, hasSuperordinateEntity, Purépecha language]
-
A.
isSupergroupOf
Indicates that one group contains another group as a proper subgroup, having strictly more members or elements than the other.
-
B.
supervisedEntityType
Indicates that one entity has the role of supervising, overseeing, or managing another entity of a specified type.
-
C.
hasPredecessorAdministrativeEntity
Indicates that one administrative entity directly preceded another in an official or organizational sequence.
-
D.
hasSubsidiaryTop
Indicates that one organization is the primary or top-level parent of another organization that operates as its subsidiary.
-
E.
hasParentUnit
chosen
Indicates that one unit is hierarchically contained within or belongs to another, higher-level unit.
- 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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 21, 2026, 1:46 p.m.