Triple
T22709245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | court-martial at Fort Meade |
E561549
|
entity |
| Predicate | verdictOnAidingTheEnemy |
P149407
|
FINISHED |
| Object | not 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: not guilty | Statement: [court-martial at Fort Meade, verdictOnAidingTheEnemy, not guilty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verdictOnAidingTheEnemy Context triple: [court-martial at Fort Meade, verdictOnAidingTheEnemy, not guilty]
-
A.
belligerentSupport
Indicates support given to a party engaged in conflict or hostilities, often implying backing one side in a belligerent or warlike context.
-
B.
allegedBelligerent
Indicates that one entity is claimed or accused of being a hostile or warring party in relation to another entity or conflict.
-
C.
attitudeTowardEnemy
Indicates the stance, feelings, or disposition that one entity holds toward an opposing or hostile entity.
-
D.
aidedOpponent
Indicates that one entity provided help or support to another entity who is considered an opponent or adversary.
-
E.
supportedDuringWar
Indicates that one entity provided assistance, resources, or backing to another entity specifically during a time of war.
- 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_69e2454f1348819088d83f420925a5c1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178d1e24881909ebd4531c0daef7f |
completed | April 29, 2026, 3:19 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:17 p.m.