Triple
T37344858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denisova Cave |
E927142
|
entity |
| Predicate | significantDiscoveryYear |
P3631
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Denisova Cave, significantDiscoveryYear, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantDiscoveryYear Context triple: [Denisova Cave, significantDiscoveryYear, 2010]
-
A.
discoveryDate
Indicates the date on which something was first discovered or identified.
-
B.
discoveredByScholarsYear
Indicates the year in which scholars discovered, identified, or formally recognized the subject.
-
C.
ageWhenDiscovered
Indicates the age of an entity at the time it was first discovered.
-
D.
historicalDiscovery
Indicates that one entity is the discoverer or originator of another entity in a historical context, capturing the act of first finding, identifying, or documenting it.
-
E.
discoveryYear
chosen
Indicates the calendar year in which something was first discovered or identified.
- 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 3, 2026, 4:16 p.m.