Triple
T541202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridget Bishop |
E12632
|
entity |
| Predicate | legalStatusAtTrial |
P7958
|
FINISHED |
| Object | found guilty |
—
|
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: found guilty | Statement: [Bridget Bishop, legalStatusAtTrial, found guilty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusAtTrial Context triple: [Bridget Bishop, legalStatusAtTrial, found guilty]
-
A.
legalStatusClarifiedBy
Indicates that the legal status of something is defined, explained, or resolved by a specific document, decision, or authoritative act.
-
B.
criminalStatus
chosen
Indicates the legal condition of an entity with respect to criminal law, such as whether they are accused, convicted, or cleared of a crime.
-
C.
hasLegalStatus
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
D.
legalOutcome
Indicates the resulting legal status, decision, or consequence that follows from a legal process, action, or judgment.
-
E.
detaineeStatus
Indicates the current legal or custodial condition of a person being detained, such as whether they are in custody, released, or under a specific detention regime.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985feee481908184a39210feab95 |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b67c308190a1a225ab7c4b74c6 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.