Triple
T32058301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | present-day Colorado |
E818677
|
entity |
| Predicate | hasArchaeologicalTradition |
P65004
|
FINISHED |
| Object | Paleoindian sites |
—
|
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: Paleoindian sites | Statement: [present-day Colorado, hasArchaeologicalTradition, Paleoindian sites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchaeologicalTradition Context triple: [present-day Colorado, hasArchaeologicalTradition, Paleoindian sites]
-
A.
hasArchaeologicalCulture
Indicates that an entity is associated with, belongs to, or is characterized by a particular archaeological culture.
-
B.
hasNearbyAncientCulture
Indicates that one entity is geographically close to another entity associated with an ancient culture or civilization.
-
C.
hasArchaeologicalFeature
Indicates that an entity possesses, contains, or is associated with a specific archaeological feature or structure.
-
D.
hasArchaeologicalSitesFrom
chosen
Indicates that an entity contains or is associated with archaeological sites dating from a specified time period or era.
-
E.
archaeologicallyExploredSince
Indicates that a place or site has been subject to archaeological exploration starting from a specified point in time.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: May 1, 2026, 12:21 a.m.