Triple
T17134315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Val Camonica |
E415796
|
entity |
| Predicate | hasEarliestRockArtPeriod |
P113262
|
FINISHED |
| Object | Epipaleolithic |
—
|
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: Epipaleolithic | Statement: [Val Camonica, hasEarliestRockArtPeriod, Epipaleolithic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEarliestRockArtPeriod Context triple: [Val Camonica, hasEarliestRockArtPeriod, Epipaleolithic]
-
A.
earliestCarvingsDateFrom
Indicates the earliest known date from which the carvings are believed to originate.
-
B.
earliestKnownPeriod
chosen
Indicates the earliest historical or temporal period in which the subject is known or documented to have existed, occurred, or been relevant.
-
C.
earliestPaintingsDateTo
Indicates the earliest known date or time period to which certain paintings can be traced or assigned.
-
D.
earliestCultEvidence
Indicates the earliest known archaeological or historical evidence for the existence of a particular cult or organized worship practice.
-
E.
hasRockCarvingsFrom
Indicates that something contains or features rock carvings that originate from a specified source, place, or period.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f02cbb7881908aa69c3443d149d5 |
completed | April 18, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.