Triple
T23705221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mongoose Gang |
E585698
|
entity |
| Predicate | supportedRegimeOf |
P32911
|
FINISHED |
| Object | Eric Gairy |
—
|
NE NERFINISHED |
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: Eric Gairy | Statement: [Mongoose Gang, supportedRegimeOf, Eric Gairy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedRegimeOf Context triple: [Mongoose Gang, supportedRegimeOf, Eric Gairy]
-
A.
supportedRegime
chosen
Indicates that an entity provided assistance, endorsement, or backing to a particular political regime or government in power.
-
B.
supportsRegulation
Indicates that one entity endorses, backs, or advocates for the implementation or continuation of a specific regulation.
-
C.
supportsRegulationBy
Indicates that one entity provides assistance, resources, or mechanisms that enable or enhance the regulatory control exerted by another entity.
-
D.
supportedRegimeType
Indicates that an entity provided backing or endorsement to a particular type of political regime.
-
E.
useRegime
Indicates a relationship where a particular method, system, or set of rules is applied or followed in carrying out an action or process.
- 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_69e24904bd508190abfcb74855de2918 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b686ef50819090a85e3ed40cfba1 |
completed | April 29, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:53 p.m.