Triple
T24467837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Sami |
E617017
|
entity |
| Predicate | ultimateAncestor |
P3891
|
FINISHED |
| Object | Proto-Uralic |
—
|
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: Proto-Uralic | Statement: [South Sami, ultimateAncestor, Proto-Uralic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ultimateAncestor Context triple: [South Sami, ultimateAncestor, Proto-Uralic]
-
A.
ancestralDomainOf
Indicates that one entity is the original or historically prior domain from which another domain is derived or descended.
-
B.
earliestKnownAncestor
chosen
Indicates that one entity is the most distant (oldest) known ancestor in the lineage of another entity.
-
C.
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.
-
D.
ancestralDomain
Indicates that one entity is the traditional or long-held territory or domain from which another entity originates or to which it is ancestrally connected.
-
E.
ancestorMother
Indicates that one entity is a female ancestor (mother, grandmother, etc.) of another entity in a family lineage.
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f299413ea88190b15e482035ff5a83 |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:20 a.m.