Triple
T33335534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond Hill Prison, Grenada |
E853523
|
entity |
| Predicate | hasNotableDetainees |
P57303
|
FINISHED |
| Object | members of the Grenada 17 |
—
|
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: members of the Grenada 17 | Statement: [Richmond Hill Prison, Grenada, hasNotableDetainees, members of the Grenada 17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableDetainees Context triple: [Richmond Hill Prison, Grenada, hasNotableDetainees, members of the Grenada 17]
-
A.
hasNotableDetaineeFuturePosition
Indicates that a detainee is associated with a future role or position considered notable or significant.
-
B.
hasPrisoners
chosen
Indicates that an entity holds or contains one or more individuals who are imprisoned or detained.
-
C.
coDetainee
Indicates that two or more individuals are detained or imprisoned together in the same facility or under the same custodial authority.
-
D.
detentionWithoutCharge
Indicates that an entity is being held in custody by authorities without having formal charges filed against them.
-
E.
hasNotablePrisonerSource
Indicates a relationship where a source provides information or evidence about a notable prisoner.
- 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01b241f7308190bedb7522cb5dc069 |
completed | May 11, 2026, 10:41 a.m. |
| PD | Predicate disambiguation | batch_6a01b19ff12c81908ee1b188b4a3e118 |
completed | May 11, 2026, 10:38 a.m. |
Created at: May 1, 2026, 1:34 a.m.