Triple
T38165174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNESCO World Heritage rock engravings in Val Camonica |
E953123
|
entity |
| Predicate | numberOfEngravedRocksApprox |
P84691
|
FINISHED |
| Object | over 2000 |
—
|
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: over 2000 | Statement: [UNESCO World Heritage rock engravings in Val Camonica, numberOfEngravedRocksApprox, over 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfEngravedRocksApprox Context triple: [UNESCO World Heritage rock engravings in Val Camonica, numberOfEngravedRocksApprox, over 2000]
-
A.
hasRockCarvingsFrom
Indicates that something contains or features rock carvings that originate from a specified source, place, or period.
-
B.
numberOfPetroglyphs
chosen
Indicates the quantity of petroglyphs associated with a given subject or location.
-
C.
numberOfRockArtSites
Indicates the count of rock art sites associated with a given subject or context.
-
D.
numberOfIndividualGeoglyphsApprox
Indicates an approximate count of distinct individual geoglyphs associated with a given subject.
-
E.
numberOfSculptures
Indicates the quantity of sculptures associated with a given entity or context.
- 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_69f76f0b93c48190a117319ab3a9f282 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.