Triple
T1488593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guanche people |
E29524
|
entity |
| Predicate | descendants |
P10101
|
FINISHED |
| Object | modern Canarian people |
—
|
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: modern Canarian people | Statement: [Guanche people, descendants, modern Canarian people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: descendants Context triple: [Guanche people, descendants, modern Canarian people]
-
A.
grandchildren
Indicates a familial relationship where one entity is the child of another entity’s child.
-
B.
successorDynasty
Indicates that one dynasty directly follows and replaces another in a sequence of rule or authority.
-
C.
modernDescendantCommunities
chosen
Indicates that certain present-day communities are descended from, or culturally/lineally continue, earlier groups or populations.
-
D.
grandchild
Indicates that one entity is the child of another entity’s child, i.e., a descendant two generations down.
-
E.
ancestor
Indicates that one entity is a forebear of another in a lineage, occurring in an earlier generation and connected through one or more parent-child relationships.
- 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_69a498da82e08190ba833330d05f380f |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6a44efc819084254614d8ea4669 |
completed | March 1, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69a4c48902808190a8028d359bcf123e |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.