Triple
T38693764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moreton Bay penal settlement |
E949937
|
entity |
| Predicate | penalClass |
P191955
|
FINISHED |
| Object | secondary punishment station |
—
|
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: secondary punishment station | Statement: [Moreton Bay penal settlement, penalClass, secondary punishment station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: penalClass Context triple: [Moreton Bay penal settlement, penalClass, secondary punishment station]
-
A.
deathPenaltyImposedFor
Indicates that a death penalty has been officially assigned as the punishment for a particular offense or action.
-
B.
isPenalInstitution
Indicates that an entity functions as a facility where individuals are legally confined as punishment or while awaiting legal proceedings.
-
C.
deathPenaltyType
Indicates the specific method or form by which a death penalty is or was carried out.
-
D.
sentencingPower
Indicates that an authority has the legal power to determine and impose a formal punishment or sentence on another party.
-
E.
partOfPenalSystem
Indicates that something belongs to, is included within, or functions as a component of a jurisdiction’s penal or criminal justice system.
- F. None of above. chosen
Provenance (4 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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69fcef636dfc819085cf91323f2e4edd |
completed | May 7, 2026, 8 p.m. |
Created at: May 3, 2026, 4:33 p.m.