Triple
T31044376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torwood Excommunication of 1680 |
E791082
|
entity |
| Predicate | declaredPenalty |
P1841
|
FINISHED |
| Object | excommunication |
—
|
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: excommunication | Statement: [Torwood Excommunication of 1680, declaredPenalty, excommunication]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declaredPenalty Context triple: [Torwood Excommunication of 1680, declaredPenalty, excommunication]
-
A.
penaltyAppliesTo
Indicates that a specific penalty is imposed on, or is relevant to, a particular entity or situation.
-
B.
penaltyMagnitude
Indicates the size or severity of a penalty imposed in a given situation or relationship.
-
C.
penaltyProvision
chosen
Indicates that a rule, contract, or law includes a clause specifying a punishment or sanction for non-compliance or violation.
-
D.
defaultPenalty
Indicates that a standard or automatically applied penalty is imposed in the absence of a specific or overridden penalty.
-
E.
penaltyMechanism
Indicates a relationship where a rule, system, or process imposes a negative consequence or sanction in response to certain actions or conditions.
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 29, 2026, 8:59 p.m.