Triple
T14621813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Billy Mitchell |
E343240
|
entity |
| Predicate | militaryCourt |
P55751
|
FINISHED |
| Object | court-martial by U.S. Army in 1925 |
—
|
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: court-martial by U.S. Army in 1925 | Statement: [Billy Mitchell, militaryCourt, court-martial by U.S. Army in 1925]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryCourt Context triple: [Billy Mitchell, militaryCourt, court-martial by U.S. Army in 1925]
-
A.
courtMartialed
chosen
Indicates that a person has been subjected to a formal military trial for alleged violations of military law.
-
B.
civilOrMilitary
Indicates that something is classified as either civil (non-military) or military in nature or function.
-
C.
militarySystem
Indicates a relationship where an entity functions as, belongs to, or is characterized by a particular military organizational or operational system.
-
D.
isCivilMilitary
Indicates that an entity or relationship involves both civilian and military components or functions.
-
E.
militaryDomain
Indicates that the relationship or action occurs within, pertains to, or is specifically associated with the military sphere 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_69d822dffc3c8190aa173b90761bffda |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb466a61c81908a110d40fb959b6f |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.