Triple
T17481914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vogelherd Cave |
E425680
|
entity |
| Predicate | firstExcavatedIn |
P86848
|
FINISHED |
| Object | 1931 |
—
|
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: 1931 | Statement: [Vogelherd Cave, firstExcavatedIn, 1931]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstExcavatedIn Context triple: [Vogelherd Cave, firstExcavatedIn, 1931]
-
A.
firstExcavationYear
chosen
Indicates the calendar year in which an excavation activity at a given site or object was first carried out.
-
B.
excavatedAt
Indicates that an excavation activity took place at a specific location or site.
-
C.
excavatedBy
Indicates that something (typically an archaeological site, artifact, or geological feature) was uncovered or dug out by a particular agent (such as a person, team, or organization).
-
D.
excavationYear
Indicates the year in which an excavation activity took place or was conducted.
-
E.
archaeologicallyExploredSince
Indicates that a place or site has been subject to archaeological exploration starting from a specified point in time.
- 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.