Triple
T32712968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nyayo House torture chambers |
E836446
|
entity |
| Predicate | cellCondition |
P29137
|
FINISHED |
| Object | overcrowded |
—
|
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: overcrowded | Statement: [Nyayo House torture chambers, cellCondition, overcrowded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cellCondition Context triple: [Nyayo House torture chambers, cellCondition, overcrowded]
-
A.
cellStates
chosen
Indicates the various conditions or phases that a cell can be in at a given time.
-
B.
cellType
Indicates the classification relationship that specifies what type of cell an entity is or is associated with.
-
C.
edgeCondition
Indicates a condition or set of criteria that must hold at the boundary or limit of a structure, process, or domain.
-
D.
cellTypeUsed
Indicates that a particular type of cell is employed or utilized in relation to another entity or process.
-
E.
canCondition
Indicates that one entity has the capability or potential to impose, apply, or bring about a particular condition on another entity or situation.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c883541c8190abff705a5658bc68 |
completed | May 3, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:11 a.m.