Triple
T11429535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neanderthals |
E270842
|
entity |
| Predicate | interbredWith |
P14611
|
FINISHED |
| Object | anatomically modern humans |
—
|
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: anatomically modern humans | Statement: [Neanderthals, interbredWith, anatomically modern humans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interbredWith Context triple: [Neanderthals, interbredWith, anatomically modern humans]
-
A.
breed
chosen
Indicates that an organism reproduces to generate offspring, typically with another organism of the same species.
-
B.
breedingFamily
Indicates that one entity belongs to or is part of the family group used for breeding or reproduction with the other entity.
-
C.
crossedWith
Indicates that one entity has moved from one side of another entity or boundary to the opposite side, typically by passing over or through it.
-
D.
breedingMethod
Indicates the technique or process by which organisms are bred or reproduced.
-
E.
contributesTraitInCrossbreeding
Indicates that a particular parent organism provides or passes on a specific trait to the offspring resulting from a crossbreeding event.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d806c1bfb881909720c74fe0fa837f |
completed | April 9, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.