Triple
T17423576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Cobham |
E423678
|
entity |
| Predicate | forfeitureReason |
P71699
|
FINISHED |
| Object | attainder for treason in some lines |
—
|
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: attainder for treason in some lines | Statement: [Baron Cobham, forfeitureReason, attainder for treason in some lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forfeitureReason Context triple: [Baron Cobham, forfeitureReason, attainder for treason in some lines]
-
A.
reasonForForfeiture
chosen
Indicates the cause or justification that led to something being surrendered, lost, or taken away.
-
B.
forfeitedBy
Indicates that something (such as a right, claim, or asset) is lost or given up as a consequence of the actions or failure of a particular entity.
-
C.
abandonedReason
Indicates the reason or cause for which something was abandoned, discontinued, or given up.
-
D.
expulsionReason
Indicates the cause or justification for which an entity was expelled from a group, place, or institution.
-
E.
reasonForAnnulment
Indicates the specific cause or grounds on which a prior decision, agreement, or status is formally annulled or declared invalid.
- 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_69d889d88b6081908bada047f5b3ba51 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44238b418819095c6a013d3ff3b17 |
completed | April 19, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.