Triple
T8758021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carib peoples |
E208120
|
entity |
| Predicate | colonialReputation |
P85224
|
FINISHED |
| Object | cannibalism |
—
|
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: cannibalism | Statement: [Carib peoples, colonialReputation, cannibalism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colonialReputation Context triple: [Carib peoples, colonialReputation, cannibalism]
-
A.
nationalReputation
Indicates the recognized standing or esteem an entity holds at the level of an entire nation.
-
B.
colonialLegacy
Indicates the enduring influence or consequences of a past colonial relationship that continue to shape interactions or conditions between entities.
-
C.
colonialEraStatus
Indicates the status or condition an entity held specifically during a colonial historical period.
-
D.
hasColonialHistory
Indicates that an entity has experienced or participated in a period of colonial rule, control, or administration in relation to another entity.
-
E.
adjustedColonialPossessionsBetween
Indicates that one entity has modified or reallocated another entity’s colonial holdings or territories in relation to a third party or reference point.
- 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_69ca835cd6b08190bd7c63db92f53c86 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5ddc2d9c81908948aee2b956cce4 |
completed | March 31, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1884bc8190a46e8308db31f7ab |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cfddef48190aee764ee7b25bae9 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:40 p.m.