Triple
T1156198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kumeyaay people |
E23787
|
entity |
| Predicate | preContactLifestyle |
P4703
|
FINISHED |
| Object | hunter-gatherer |
—
|
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: hunter-gatherer | Statement: [Kumeyaay people, preContactLifestyle, hunter-gatherer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preContactLifestyle Context triple: [Kumeyaay people, preContactLifestyle, hunter-gatherer]
-
A.
primaryFunctionInPrehistory
Indicates the main role or use an entity had during prehistoric times, before written records.
-
B.
firstContactWithEuropeans
Indicates that this marks the initial recorded encounter or interaction between a group and European people.
-
C.
inhabitedSince
Indicates that a place has been continuously or initially occupied or lived in by someone or something starting from a specified time.
-
D.
hadPrimarySettlementPattern
Indicates that an entity exhibited or was characterized by a particular dominant form or arrangement of human settlement.
-
E.
traditionalLifestyle
chosen
Indicates that an entity follows or maintains long-established customs, practices, and ways of living, typically in contrast to modern or industrialized lifestyles.
- 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_69a493f0d32c8190ac74bad3c87f2641 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc912300819084c9c69783055a70 |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb50d19c81908a98dbbb04a8906f |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.