Triple
T9158853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cumberland culture |
E219770
|
entity |
| Predicate | hasHuntingTechnology |
P3047
|
FINISHED |
| Object | spear and atlatl system |
—
|
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: spear and atlatl system | Statement: [Cumberland culture, hasHuntingTechnology, spear and atlatl system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHuntingTechnology Context triple: [Cumberland culture, hasHuntingTechnology, spear and atlatl system]
-
A.
hasTechnique
chosen
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
B.
huntingTime
Indicates the time period during which a hunting activity takes place or is scheduled.
-
C.
isTechHeavy
Indicates that something involves a high degree of technology use, complexity, or dependence.
-
D.
huntingStyle
Indicates the characteristic manner or method an entity typically uses when hunting.
-
E.
hunting
Indicates one entity actively pursuing and attempting to capture or kill another entity, typically as prey.
- 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_69ca83e25418819093c6503deeaf30de |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca9d805588190a0deadda1dd410a1 |
completed | April 1, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69cc6605c6808190a30d92da006206ac |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:21 p.m.