Triple
T7052785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simonside Hills |
E164006
|
entity |
| Predicate | hasRockArtNearby |
P14422
|
FINISHED |
| Object | prehistoric cup-and-ring marks |
—
|
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: prehistoric cup-and-ring marks | Statement: [Simonside Hills, hasRockArtNearby, prehistoric cup-and-ring marks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRockArtNearby Context triple: [Simonside Hills, hasRockArtNearby, prehistoric cup-and-ring marks]
-
A.
hasRockArtSubject
Indicates that something features or is associated with a particular subject depicted in rock art.
-
B.
hasRockCarvingsFrom
Indicates that something contains or features rock carvings that originate from a specified source, place, or period.
-
C.
hasRockReliefSite
Indicates a relationship where a subject is associated with, contains, or is the location of a rock relief site.
-
D.
hasNearbyArchaeologicalSite
chosen
Indicates that an entity is located close to or in the vicinity of an archaeological site.
-
E.
rockArtLocationType
Indicates the specific type or category of location where rock art is found or situated.
- 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_69c68861678881909961ddf4d779f750 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e4a3c36c819080942c59f1830ae8 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bdc1f08190975fcdbbb1854d1e |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:37 p.m.