Triple
T6124338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | court-martial of William Calley |
E136558
|
entity |
| Predicate | hasDefendantRank |
P55567
|
FINISHED |
| Object | First Lieutenant |
—
|
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: First Lieutenant | Statement: [court-martial of William Calley, hasDefendantRank, First Lieutenant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDefendantRank Context triple: [court-martial of William Calley, hasDefendantRank, First Lieutenant]
-
A.
defendantRank
chosen
Indicates the hierarchical position or status assigned to a defendant relative to other defendants in a legal case.
-
B.
hasDefendants
Indicates that one or more entities serve as defendants in relation to a particular legal case or proceeding.
-
C.
hasLegalRank
Indicates that an entity holds a specific legal status, classification, or rank within a formal legal or regulatory system.
-
D.
defendantStatus
Indicates the legal condition or standing of a defendant within a judicial or law-enforcement process.
-
E.
courtRank
Indicates the formal hierarchical rank or status an individual holds within a court or courtly system.
- 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_69c0089f851c81909e5e189a617dcff6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05c25976081909e0a40e07dff0b8a |
completed | March 22, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69c049f9ab3c81909c8ab6466f6a2935 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:14 p.m.