Triple
T10764260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanum World Heritage Site |
E253911
|
entity |
| Predicate | hasRockCarvingsFromPeriod |
P38612
|
FINISHED |
| Object | Bronze Age |
—
|
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: Bronze Age | Statement: [Tanum World Heritage Site, hasRockCarvingsFromPeriod, Bronze Age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRockCarvingsFromPeriod Context triple: [Tanum World Heritage Site, hasRockCarvingsFromPeriod, Bronze Age]
-
A.
hasRockCarvingsFrom
chosen
Indicates that something contains or features rock carvings that originate from a specified source, place, or period.
-
B.
hasArchaeologicalRemainsFromPeriod
Indicates that an entity contains or preserves archaeological remains originating from a specified historical period.
-
C.
hasRockArtSubject
Indicates that something features or is associated with a particular subject depicted in rock art.
-
D.
eraOfOriginalMonuments
Indicates the historical time period during which the original monuments were created or first established.
-
E.
hasCarvings
Indicates that one entity features or contains carved designs or engravings on its surface, created by another entity or process.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d731a504948190943f0e27c0d891ed |
completed | April 9, 2026, 4:57 a.m. |
| PD | Predicate disambiguation | batch_69d6f311529c819080ca5493d55d6050 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:16 p.m.