Triple
T17481930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vogelherd Cave |
E425680
|
entity |
| Predicate | datingFrom |
P52397
|
FINISHED |
| Object | about 40,000 years ago |
—
|
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 ago | Statement: [Vogelherd Cave, datingFrom, about 40,000 years ago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: datingFrom Context triple: [Vogelherd Cave, datingFrom, about 40,000 years ago]
-
A.
likelyDatingFrom
chosen
Indicates that something is estimated or believed to originate from, or have begun in, a particular time period or date.
-
B.
establishedFrom
Indicates that something was created, founded, or formed starting from a specified source, origin, or prior entity.
-
C.
entryDate
Indicates the date on which an entity was first recorded, created, or entered into a system or context.
-
D.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
E.
hasBeenDatedBy
Indicates that one entity has previously been in a romantic or dating relationship with another entity.
- 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451c0db14819098922453131fb40a |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.