Triple
T12355428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Styer |
E294598
|
entity |
| Predicate | caseInvolves |
P41134
|
FINISHED |
| Object | legal responsibility of military commanders |
—
|
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: legal responsibility of military commanders | Statement: [Styer, caseInvolves, legal responsibility of military commanders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseInvolves Context triple: [Styer, caseInvolves, legal responsibility of military commanders]
-
A.
involvesIssue
Indicates that an action, event, or entity is related to, concerns, or includes a particular issue.
-
B.
involves
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
-
C.
disputeInvolves
Indicates that a particular dispute includes or concerns the specified entities as participants or parties to the conflict.
-
D.
judgmentInvolves
chosen
Indicates that a particular judgment, decision, or legal ruling includes, concerns, or pertains to a specified entity or matter.
-
E.
constantInvolved
Indicates that a constant participates in or is directly involved in the specified relation, operation, or context.
- 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d942a2d6e08190a13c7ff89af09354 |
completed | April 10, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69d93ecf6b548190a394b6b56a0c1c68 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.