Triple
T29918040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Petroglyph Canyon |
E759844
|
entity |
| Predicate | hasPetroglyphTechnique |
P164989
|
FINISHED |
| Object | pecked designs |
—
|
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: pecked designs | Statement: [Big Petroglyph Canyon, hasPetroglyphTechnique, pecked designs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPetroglyphTechnique Context triple: [Big Petroglyph Canyon, hasPetroglyphTechnique, pecked designs]
-
A.
hasTechnique
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
B.
numberOfPetroglyphs
Indicates the quantity of petroglyphs associated with a given subject or location.
-
C.
hasCarvings
Indicates that one entity features or contains carved designs or engravings on its surface, created by another entity or process.
-
D.
hasRockArtForm
chosen
Indicates that something possesses or is associated with a particular form or type of rock art.
-
E.
hasTypicalInscriptionMethod
Indicates the usual or characteristic method by which inscriptions are applied or created on an object or surface.
- 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_69f2246189fc8190996b63ee1f9a2374 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: April 29, 2026, 6:13 p.m.