Triple
T30868648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clovis culture |
E786274
|
entity |
| Predicate | typeSiteLocation |
P170237
|
FINISHED |
| Object | near Clovis, New Mexico |
—
|
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: near Clovis, New Mexico | Statement: [Clovis culture, typeSiteLocation, near Clovis, New Mexico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeSiteLocation Context triple: [Clovis culture, typeSiteLocation, near Clovis, New Mexico]
-
A.
typeSite
Indicates that a site is classified as being of a particular type or category.
-
B.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
-
C.
isTypeSiteOf
chosen
Indicates that a site serves as the specific location or setting where a particular type, category, or classification is realized or occurs.
-
D.
isSiteOf
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
-
E.
engineeringLocation
Indicates the place where engineering-related work, design, or technical development for an entity is carried out.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f691cfeaa881908939a30f971ceec0 |
completed | May 3, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:47 p.m.