Triple
T29917978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coso Rock Art District |
E759843
|
entity |
| Predicate | mostIntensiveUsePeriod |
P4017
|
FINISHED |
| Object | circa 2000 BCE to 1000 CE |
—
|
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: circa 2000 BCE to 1000 CE | Statement: [Coso Rock Art District, mostIntensiveUsePeriod, circa 2000 BCE to 1000 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mostIntensiveUsePeriod Context triple: [Coso Rock Art District, mostIntensiveUsePeriod, circa 2000 BCE to 1000 CE]
-
A.
maximumPeriod
Indicates that there is an upper bound on the duration or time interval for which a given condition, state, or relationship can hold.
-
B.
periodOfMajorUse
chosen
Indicates the time span during which something was primarily or most intensively used.
-
C.
intensiveUse
Indicates a relationship where an entity is used in a concentrated, frequent, or high-intensity manner by another entity.
-
D.
timeOfMostIntenseStudy
Indicates the specific time period during which an entity engages in its highest level of study intensity.
-
E.
bestKnownPeriod
Indicates the time period for which an entity is most prominently recognized or most widely associated.
- 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_69f6779140408190987216918cfaf0cb |
completed | May 2, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:13 p.m.