Triple
T21870365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atayal people |
E539983
|
entity |
| Predicate | colonialPolicyImpact |
P128657
|
FINISHED |
| Object | suppression of head-hunting |
—
|
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: suppression of head-hunting | Statement: [Atayal people, colonialPolicyImpact, suppression of head-hunting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colonialPolicyImpact Context triple: [Atayal people, colonialPolicyImpact, suppression of head-hunting]
-
A.
impactOnColonies
Indicates the effect or influence that one factor, event, or condition has on colonies.
-
B.
impactOfColonization
chosen
Indicates the effects or consequences that colonization has on a particular entity, group, or context.
-
C.
colonialPolicyFeature
Indicates a characteristic, practice, or component that forms part of a colonial policy or system of colonial governance.
-
D.
colonialLegacy
Indicates the enduring influence or consequences of a past colonial relationship that continue to shape interactions or conditions between entities.
-
E.
colonialChange
Indicates a change in colonial status or control of a territory, such as gaining, losing, or altering colonial rule.
- 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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0f33509d08190b33775abb84d5255 |
completed | April 28, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:57 p.m.