Triple
T27079396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homo naledi |
E685550
|
entity |
| Predicate | numberOfSpecimensRecovered |
P48557
|
FINISHED |
| Object | over 1500 fossil elements |
—
|
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: over 1500 fossil elements | Statement: [Homo naledi, numberOfSpecimensRecovered, over 1500 fossil elements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfSpecimensRecovered Context triple: [Homo naledi, numberOfSpecimensRecovered, over 1500 fossil elements]
-
A.
numberOfSurvivingSpecimens
Indicates the count of individual specimens that remain alive or intact after a particular event, period, or condition.
-
B.
collectedSpecimensIn
Indicates that an entity gathered or obtained specimens within a specified location or context.
-
C.
collectedSpecimensFor
Indicates that one entity gathered or obtained specimens on behalf of or for the benefit of another entity.
-
D.
numberOfBonesRecovered
chosen
Indicates the count of bones that have been found and recovered in relation to a particular subject or event.
-
E.
numberOfSpecies
Indicates the count of distinct species associated with a given entity or context.
- 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_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
Created at: April 27, 2026, 8:33 a.m.