Triple
T23389787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cueva de las Manos |
E593981
|
entity |
| Predicate | earliestArtDate |
P58296
|
FINISHED |
| Object | circa 9000 BCE |
—
|
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: circa 9000 BCE | Statement: [Cueva de las Manos, earliestArtDate, circa 9000 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestArtDate Context triple: [Cueva de las Manos, earliestArtDate, circa 9000 BCE]
-
A.
earliestPaintingsDateTo
chosen
Indicates the earliest known date or time period to which certain paintings can be traced or assigned.
-
B.
earliestCarvingsDateFrom
Indicates the earliest known date from which the carvings are believed to originate.
-
C.
artifactsDatedTo
Indicates that certain artifacts have been assigned or associated with a specific date or time period.
-
D.
earliestFindsDateTo
Indicates the earliest known date at which the finding, discovery, or observation of one entity is recorded as relating to another entity.
-
E.
earliestKnownPeriod
Indicates the earliest historical or temporal period in which the subject is known or documented to have existed, occurred, or been relevant.
- 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a49a7c14819082aab826715976c5 |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:35 p.m.