Triple
T3814961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | court-martial of General Charles Lee |
E84229
|
entity |
| Predicate | accusedRank |
P52029
|
FINISHED |
| Object | major general |
—
|
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: major general | Statement: [court-martial of General Charles Lee, accusedRank, major general]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accusedRank Context triple: [court-martial of General Charles Lee, accusedRank, major general]
-
A.
accusedIn
Indicates that a person or entity is formally charged with wrongdoing in a particular case, proceeding, or context.
-
B.
accusedOf
Indicates that one entity has formally alleged or claimed that another entity committed a specific wrongdoing or offense.
-
C.
accusedGroup
Indicates that one group is formally charged or blamed by another party for committing a wrongdoing or offense.
-
D.
firstAccused
Indicates that the subject is the primary or earliest individual formally charged or blamed in a particular case or incident.
-
E.
numberOfPeopleAccused
Indicates the count of individuals who are formally alleged to have committed a particular act or offense.
- 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_69aed931f5908190be2c07af66d4df25 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7482d708190a3ec74745b102a4c |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aef14f9bb4819098e64b527b546d74 |
completed | March 9, 2026, 4:11 p.m. |
Created at: March 9, 2026, 3:17 p.m.