Triple
T35008198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jump City Prison |
E1009870
|
entity |
| Predicate | typicalInmates |
P160682
|
FINISHED |
| Object | superpowered criminals |
—
|
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: superpowered criminals | Statement: [Jump City Prison, typicalInmates, superpowered criminals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalInmates Context triple: [Jump City Prison, typicalInmates, superpowered criminals]
-
A.
inmates
Indicates that one entity is confined or held as a prisoner within an institution or facility associated with another entity.
-
B.
mainInmates
chosen
Indicates that the referenced entities are the primary or principal inmates associated with a particular facility, case, or context.
-
C.
prisonType
Indicates the specific category or classification of a prison associated with an entity.
-
D.
prisonerType
Indicates the classification or category assigned to a prisoner within a correctional or detention system.
-
E.
securityForInmates
Indicates the provision or management of protective measures and safeguards specifically intended for inmates.
- 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_69f76dcb716881909f75e4fd60ab2284 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.