Triple
T37282394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mezmaiskaya Cave |
E925432
|
entity |
| Predicate | yielded |
P99909
|
FINISHED |
| Object | mitochondrial DNA of Neanderthals |
—
|
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: mitochondrial DNA of Neanderthals | Statement: [Mezmaiskaya Cave, yielded, mitochondrial DNA of Neanderthals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yielded Context triple: [Mezmaiskaya Cave, yielded, mitochondrial DNA of Neanderthals]
-
A.
yieldedStone
Indicates that one entity produced, provided, or gave rise to a particular stone as a result or outcome.
-
B.
hasYield
Indicates that one entity produces, returns, or generates a measurable output, result, or profit for another entity or context.
-
C.
emitted
Indicates that one entity has released, discharged, or sent out another entity, such as energy, particles, signals, or substances, into its surroundings.
-
D.
yieldedTaxon
chosen
Indicates that one entity produced, revealed, or resulted in the discovery or identification of a particular taxon.
-
E.
achieved
Indicates that an entity successfully reached, obtained, or accomplished a specified goal, result, or state.
- 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_69f76eafe20c8190856d3b996a4c31a7 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.