Triple
T32344887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael James Elstad |
E826429
|
entity |
| Predicate | partyTypeInCase |
P113446
|
FINISHED |
| Object | respondent (at trial level) |
—
|
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: respondent (at trial level) | Statement: [Michael James Elstad, partyTypeInCase, respondent (at trial level)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partyTypeInCase Context triple: [Michael James Elstad, partyTypeInCase, respondent (at trial level)]
-
A.
partyCategory
Indicates the classification or type assigned to a party within a given context or system.
-
B.
party
Indicates that an entity participates as a side or participant in an event, agreement, or situation.
-
C.
typicalParty
Indicates that an entity is a usual, standard, or characteristic participant in a given type of event, situation, or relationship.
-
D.
partyLed
Indicates that one entity serves as the leader or head of a particular party, organization, or group.
-
E.
partyTypeOfRespondent
chosen
Indicates the specific legal or procedural role that the respondent plays as a party in a case or proceeding.
- 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: May 1, 2026, 12:48 a.m.