Triple
T28529481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humphrey’s Executor |
E722000
|
entity |
| Predicate | partyInCaseType |
P15954
|
FINISHED |
| Object | U.S. Supreme Court case |
—
|
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: U.S. Supreme Court case | Statement: [Humphrey’s Executor, partyInCaseType, U.S. Supreme Court case]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partyInCaseType Context triple: [Humphrey’s Executor, partyInCaseType, U.S. Supreme Court case]
-
A.
partyToCase
chosen
Indicates that an entity is involved in a legal case as one of its formal participants (e.g., plaintiff, defendant, or other party).
-
B.
partyTypePlaintiffs
Indicates the classification or category of the parties serving as plaintiffs in a legal action.
-
C.
partiesAre
Indicates that certain entities are the participants or sides involved in a particular relationship, agreement, or event.
-
D.
partyTypeOfRespondent
Indicates the specific legal or procedural role that the respondent plays as a party in a case or proceeding.
-
E.
partOfCase
Indicates that something is a component, element, or sub-issue belonging to or contained within a larger case.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 28, 2026, 3:27 a.m.