Triple
T17583765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hohle Fels |
E428266
|
entity |
| Predicate | notableArtifactAge |
P11951
|
FINISHED |
| Object | about 40,000 years |
—
|
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: about 40,000 years | Statement: [Hohle Fels, notableArtifactAge, about 40,000 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableArtifactAge Context triple: [Hohle Fels, notableArtifactAge, about 40,000 years]
-
A.
artifactsDatedTo
Indicates that certain artifacts have been assigned or associated with a specific date or time period.
-
B.
archaeologicalEvidenceAge
chosen
Indicates the age or time period to which a piece of archaeological evidence is dated.
-
C.
eraOfOriginalMonuments
Indicates the historical time period during which the original monuments were created or first established.
-
D.
isAncient
Indicates that the entity existed or originated in a very distant past, typically far earlier than the commonly referenced historical period.
-
E.
estimatedYearOfCreation
Indicates the year in which something is believed or approximated to have been created, rather than a precisely known creation year.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e463d015fc8190b2dd897026d6fcb5 |
completed | April 19, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.