Triple
T26082408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States v. Colson |
E657880
|
entity |
| Predicate | involvesRoleOfDefendant |
P171397
|
FINISHED |
| Object | former White House aide |
—
|
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: former White House aide | Statement: [United States v. Colson, involvesRoleOfDefendant, former White House aide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesRoleOfDefendant Context triple: [United States v. Colson, involvesRoleOfDefendant, former White House aide]
-
A.
defendant
Indicates that an entity is the party accused or sued in a legal action or proceeding.
-
B.
coDefendant
Indicates that two or more parties are jointly named and involved as defendants in the same legal case or proceeding.
-
C.
constantInvolved
Indicates that a constant participates in or is directly involved in the specified relation, operation, or context.
-
D.
roleAtCourt
Indicates the specific position, function, or status an entity holds within a court or courtly setting.
-
E.
involvedCourt
Indicates that a specific court participates in, has jurisdiction over, or is otherwise formally associated with a given legal case or proceeding.
- 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 26, 2026, 7:39 p.m.