Triple
T22117051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taung Child |
E546570
|
entity |
| Predicate | estimatedAgeRangeInYears |
P2736
|
FINISHED |
| Object | 2000000–3000000 |
—
|
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: 2000000–3000000 | Statement: [Taung Child, estimatedAgeRangeInYears, 2000000–3000000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedAgeRangeInYears Context triple: [Taung Child, estimatedAgeRangeInYears, 2000000–3000000]
-
A.
hasApproximateAgeRange
Indicates that one entity is associated with another entity representing an estimated or non-exact span of ages.
-
B.
ageRange
chosen
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
C.
containsAge
Indicates that one entity includes or specifies the age value or age-related information of another entity.
-
D.
supportsAgeRange
Indicates that one entity is compatible with, valid for, or designed to accommodate a specified range of ages.
-
E.
approximateStartAge
Indicates the estimated or roughly determined age at which an event, condition, or state begins.
- 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_69e11e38b3848190ac3a4fa97d56e65a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1294e85708190b455846bacbdfd03 |
completed | April 28, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:31 p.m.