Triple
T27079412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homo naledi |
E685550
|
entity |
| Predicate | publicationYearOfDating |
P123591
|
FINISHED |
| Object | 2017 for direct dating results |
—
|
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: 2017 for direct dating results | Statement: [Homo naledi, publicationYearOfDating, 2017 for direct dating results]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicationYearOfDating Context triple: [Homo naledi, publicationYearOfDating, 2017 for direct dating results]
-
A.
originYear
Indicates the year in which something first originated, was created, or began.
-
B.
publicationYear
Indicates the specific calendar year in which a work was formally published or released.
-
C.
dataReleaseYear
chosen
Indicates the year in which the data was officially released or made publicly available.
-
D.
yearCirca
Indicates that the associated year is approximate or uncertain rather than exact.
-
E.
yearOfReference
Indicates the specific year to which a statement, measurement, or data point is intended to apply or be interpreted with reference.
- 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_69ef14843b1481909d828b3d5a44550a |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 27, 2026, 8:33 a.m.