Triple
T15163221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Costanoan people |
E362267
|
entity |
| Predicate | culturalRegionOverlap |
P93335
|
FINISHED |
| Object | neighboring Miwok peoples |
—
|
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: neighboring Miwok peoples | Statement: [Costanoan people, culturalRegionOverlap, neighboring Miwok peoples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culturalRegionOverlap Context triple: [Costanoan people, culturalRegionOverlap, neighboring Miwok peoples]
-
A.
culturalRegion
Indicates that an entity is located in, associated with, or belongs to a specific cultural region or cultural area.
-
B.
geographicOverlap
chosen
Indicates that two geographic areas share at least part of the same physical space or territory.
-
C.
culturalAreaIncludes
Indicates that a broader cultural area encompasses or contains a smaller cultural region or entity within its scope.
-
D.
culturallySimilarTo
Indicates that two entities share comparable cultural characteristics, practices, or values.
-
E.
regionOfCulturalImpact
Indicates the geographic area where an entity’s cultural influence, activities, or effects are most significantly felt or observed.
- 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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0064b21ac81908b793bdbd741bcd8 |
completed | April 15, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:08 a.m.