Triple
T23871271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bagne of Toulon |
E592735
|
entity |
| Predicate | hasTypeOfPunishment |
P99542
|
FINISHED |
| Object | hard labor |
—
|
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: hard labor | Statement: [Bagne of Toulon, hasTypeOfPunishment, hard labor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfPunishment Context triple: [Bagne of Toulon, hasTypeOfPunishment, hard labor]
-
A.
hasPunishment
Indicates that an entity is subject to a specified penalty, sanction, or adverse consequence as a result of some action, condition, or rule.
-
B.
punishedBy
Indicates that an entity receives punishment administered by another entity.
-
C.
punishmentIncludes
Indicates that a specified punishment encompasses or contains another specified punitive measure as one of its components.
-
D.
authorizesPunishment
Indicates that one entity grants permission or legal authority for another entity to impose a punishment.
-
E.
punishmentMethod
chosen
Indicates the method or means by which a punishment is carried out on an entity.
- 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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cbfe1f948190ad2c0d5bbe0c7240 |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:14 p.m.