Triple
T15338280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roswell Field |
E366723
|
entity |
| Predicate | roleInDredScottCase |
P16985
|
FINISHED |
| Object | filed federal suit on behalf of Dred Scott |
—
|
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: filed federal suit on behalf of Dred Scott | Statement: [Roswell Field, roleInDredScottCase, filed federal suit on behalf of Dred Scott]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInDredScottCase Context triple: [Roswell Field, roleInDredScottCase, filed federal suit on behalf of Dred Scott]
-
A.
legalCaseRole
chosen
Indicates the specific role or capacity an entity holds within a legal case, such as plaintiff, defendant, judge, or attorney.
-
B.
roleInEmmettTillCase
Indicates that one entity had a specific role or involvement in the historical case surrounding Emmett Till.
-
C.
roleAtCourt
Indicates the specific position, function, or status an entity holds within a court or courtly setting.
-
D.
deJureRole
Indicates that an entity holds a role or position by law or formal right, regardless of whether it is exercised in practice.
-
E.
courtRole
Indicates the specific capacity or position an entity holds within a court proceeding or judicial 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e11b22c81908280efe65acd5454 |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:17 a.m.