Triple
T21443914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Dominick |
E529018
|
entity |
| Predicate | mutinyParticipants |
P59854
|
FINISHED |
| Object | enslaved Africans |
—
|
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: enslaved Africans | Statement: [San Dominick, mutinyParticipants, enslaved Africans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mutinyParticipants Context triple: [San Dominick, mutinyParticipants, enslaved Africans]
-
A.
roleInMutiny
chosen
Indicates that one entity participated in a mutiny with a specific role or capacity in that rebellious action.
-
B.
placeOfMutiny
Indicates the location where a mutiny occurred or took place.
-
C.
overthrowParticipants
Indicates that the related entities are participants involved in carrying out or attempting an overthrow of an existing authority or regime.
-
D.
coupParticipantIn
Indicates that an entity took part in, contributed to, or was involved in carrying out a specific coup event.
-
E.
metConspiratorsAt
Indicates that an individual met with one or more co-conspirators at a specific place and/or time as part of a conspiracy.
- 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_69e0c4569fa081908101baa24f8745db |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b7055d148190ae3b52e10abd8fd2 |
completed | April 22, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:05 p.m.