Triple
T938141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pequot people |
E20243
|
entity |
| Predicate | colonialEraStatus |
P21963
|
FINISHED |
| Object | powerful regional tribe |
—
|
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: powerful regional tribe | Statement: [Pequot people, colonialEraStatus, powerful regional tribe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colonialEraStatus Context triple: [Pequot people, colonialEraStatus, powerful regional tribe]
-
A.
preColonialStatus
Indicates the condition, role, or social-political standing an entity held prior to the onset of colonial rule.
-
B.
hasColonialHistoryWith
Indicates that one entity has a historical relationship of colonization or being colonized involving the other entity.
-
C.
hadColonialAdministrationType
Indicates the specific form or system of colonial governance that was exercised over a territory or population.
-
D.
colonialPeriodEnd
Indicates the time or event at which a colonial period or colonial rule over a territory comes to an end.
-
E.
colonialLegacy
Indicates the enduring influence or consequences of a past colonial relationship that continue to shape interactions or conditions between entities.
- 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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b388f0bc8190a087222636135ba5 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b29c68f48190aecad10e351a99de |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b344f6f48190ba03ce593c94176b |
completed | March 1, 2026, 9:44 p.m. |
Created at: March 1, 2026, 7:40 p.m.