Triple
T10370613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huastec language |
E244371
|
entity |
| Predicate | hasAncestralRelation |
P369
|
FINISHED |
| Object | Proto-Mayan language |
—
|
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: Proto-Mayan language | Statement: [Huastec language, hasAncestralRelation, Proto-Mayan language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAncestralRelation Context triple: [Huastec language, hasAncestralRelation, Proto-Mayan language]
-
A.
hasAncestor
chosen
Indicates that one entity is an ancestor (direct or indirect, such as a parent, grandparent, etc.) of another entity in a genealogical or hierarchical lineage.
-
B.
relationToAncestors
Indicates a familial relationship that connects an entity to one or more of its ancestors in a lineage or hierarchy.
-
C.
hasAncestralRoots
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
-
D.
hasGenealogicalRelation
Indicates that there exists a family or ancestry-based relationship (such as parent, child, sibling, or more distant kinship) between the related entities.
-
E.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9737cfc81909d6302bd4177d186 |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dface5508190a7b42f01ad0a19a2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 12:01 p.m.