Triple
T798876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Rosa Island |
E17082
|
entity |
| Predicate | hasEvidenceOfHumanOccupation |
P11951
|
FINISHED |
| Object | over 10,000 years |
—
|
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: over 10,000 years | Statement: [Santa Rosa Island, hasEvidenceOfHumanOccupation, over 10,000 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEvidenceOfHumanOccupation Context triple: [Santa Rosa Island, hasEvidenceOfHumanOccupation, over 10,000 years]
-
A.
archaeologicalEvidenceAge
chosen
Indicates the age or time period to which a piece of archaeological evidence is dated.
-
B.
hasArchaeologicalValue
Indicates that something possesses significance or worth in the study, preservation, or interpretation of past human activity through material remains.
-
C.
excavatedAt
Indicates that an excavation activity took place at a specific location or site.
-
D.
hasNearbyArchaeologicalSite
Indicates that an entity is located close to or in the vicinity of an archaeological site.
-
E.
historicallyInhabitedBy
Indicates that a place or region was inhabited by a particular group or population during some period in the past.
- 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_69a49378b9c48190adbf5f62e5b7aca1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a7b4d9548190aad5fdf1211cf8cd |
completed | March 1, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69a4a5122a008190b0c621b7bc588d41 |
completed | March 1, 2026, 8:44 p.m. |
Created at: March 1, 2026, 7:38 p.m.