Triple
T37291428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denisova Cave finger bone |
E925674
|
entity |
| Predicate | genomeSequencedBy |
P187707
|
FINISHED |
| Object | Svante Pääbo |
—
|
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: Svante Pääbo | Statement: [Denisova Cave finger bone, genomeSequencedBy, Svante Pääbo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genomeSequencedBy Context triple: [Denisova Cave finger bone, genomeSequencedBy, Svante Pääbo]
-
A.
genomeSequencedFor
Indicates that the complete or partial genetic sequence of one entity has been determined specifically for or in relation to another entity.
-
B.
genomeSequenced
Indicates that the complete DNA sequence of an organism’s genome has been determined and recorded.
-
C.
genomeSequencedYear
Indicates the calendar year in which the genome of the referenced organism or biological entity was sequenced.
-
D.
usesSequencingTechnology
Indicates that one entity employs or applies sequencing technology to perform an action or achieve a result involving another entity.
-
E.
genomeSource
Indicates the origin or provenance of a genome, specifying where or how the genomic data was obtained.
- F. None of above. chosen
Provenance (4 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_69f76eb0f86c819098dee07393e69ec3 |
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. |
| PDg | Predicate description generation | batch_69fb78c982ac8190846efe8f6209e5d1 |
completed | May 6, 2026, 5:22 p.m. |
Created at: May 3, 2026, 4:16 p.m.