Triple
T6314914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seediq people |
E141590
|
entity |
| Predicate | warCustom |
P70008
|
FINISHED |
| Object | Head-taking as proof of valor (historical) |
—
|
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: Head-taking as proof of valor (historical) | Statement: [Seediq people, warCustom, Head-taking as proof of valor (historical)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warCustom Context triple: [Seediq people, warCustom, Head-taking as proof of valor (historical)]
-
A.
warCry
Indicates a relationship where an entity utters or performs a loud, rallying shout or chant intended to inspire allies or intimidate opponents, typically in a conflict or competitive context.
-
B.
warName
Indicates the specific name or title assigned to a particular war or armed conflict.
-
C.
warPeriod
Indicates a time span during which a state of war or armed conflict is ongoing between parties.
-
D.
warAim
Indicates the strategic objective or intended outcome that a party seeks to achieve through engaging in war or armed conflict.
-
E.
warfareType
Indicates the specific kind or category of warfare that characterizes a given conflict or military engagement.
- F. None of above. chosen
Provenance (4 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_69c008d13b8c8190be47d896eb735605 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064a197488190946c4637b3c829a5 |
completed | March 22, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69c060e5efc48190861b8266e5b0cc0c |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623bb29081908bfdfb84a07ece90 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:28 p.m.