Triple
T34057620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petroglyph Point |
E873404
|
entity |
| Predicate | timePeriodOfMostPetroglyphs |
P188127
|
FINISHED |
| Object | late prehistoric period |
—
|
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: late prehistoric period | Statement: [Petroglyph Point, timePeriodOfMostPetroglyphs, late prehistoric period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfMostPetroglyphs Context triple: [Petroglyph Point, timePeriodOfMostPetroglyphs, late prehistoric period]
-
A.
approximateLatestPetroglyphDate
Indicates the estimated most recent date at which the petroglyphs were created or modified.
-
B.
numberOfPetroglyphs
Indicates the quantity of petroglyphs associated with a given subject or location.
-
C.
earliestPetroglyphsDateTo
Indicates that the earliest known petroglyphs associated with an entity originate from or can be dated to a specified time or period.
-
D.
numberOfIndividualGeoglyphsApprox
Indicates an approximate count of distinct individual geoglyphs associated with a given subject.
-
E.
timePeriodOfBurials
Indicates the span of time during which the burials associated with an entity took place.
- F. None of above. chosen
Provenance (4 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_69f349a3ec2c8190b62da76e54231a0f |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fba28684208190921694f23e350c3b |
completed | May 6, 2026, 8:20 p.m. |
Created at: May 1, 2026, 1:52 a.m.