Triple
T8251366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltimore Plot |
E192964
|
entity |
| Predicate | hasPerpetrators |
P81195
|
FINISHED |
| Object | pro-Southern conspirators |
—
|
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: pro-Southern conspirators | Statement: [Baltimore Plot, hasPerpetrators, pro-Southern conspirators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerpetrators Context triple: [Baltimore Plot, hasPerpetrators, pro-Southern conspirators]
-
A.
numberOfPerpetrators
Indicates the count of distinct individuals who carried out or participated in a particular act, event, or offense.
-
B.
hasPerpetratorOrigin
Indicates that the origin or source of a perpetrator (such as their nationality, place of birth, or background) is associated with a particular event, action, or crime.
-
C.
hasPerpetratorStatement
Indicates that a statement has been made by the perpetrator regarding the related event or action.
-
D.
perpetratedBy
Indicates that an action, event, or wrongdoing was carried out or caused by a particular agent or entity.
-
E.
perpetratorStatus
Indicates the role or condition of an individual in relation to committing or being responsible for a specific harmful or criminal act.
- 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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78c935408190b9196a849a8d3a3e |
completed | March 31, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69cb36b6d5548190b665a6cce14c69f7 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb44d1caa881909069fa925a91316b |
completed | March 31, 2026, 3:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.