Triple
T25839074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ötzi the Iceman |
E650884
|
entity |
| Predicate | yHaplogroup |
P77019
|
FINISHED |
| Object | G2a |
—
|
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: G2a | Statement: [Ötzi the Iceman, yHaplogroup, G2a]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yHaplogroup Context triple: [Ötzi the Iceman, yHaplogroup, G2a]
-
A.
ancestralSubgroups
Indicates that one group consists of or descends from earlier, foundational subgroups within a lineage or hierarchy.
-
B.
ancestralGroup
Indicates that one entity is a broader ancestral lineage, population, or group from which the other entity descends or originates.
-
C.
geneticOrigin
Indicates that one entity is the source or contributor of another entity’s genetic material or hereditary traits.
-
D.
genealogicalClassification
chosen
Indicates a relationship where one entity is categorized within a family or lineage structure relative to another, based on genealogical or ancestral connections.
-
E.
sharesDNAWithHumans
Indicates that one entity possesses genetic material that is evolutionarily related to, and partially identical with, that of humans.
- 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_69e7ab38086081908f3a8e7e0c6efd83 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f601f80b9c8190947c4542654455a6 |
completed | May 2, 2026, 1:54 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 7:49 a.m.