Triple
T11744368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kellie Miller |
E279237
|
entity |
| Predicate | legalActionIn |
P89736
|
FINISHED |
| Object | federal court |
—
|
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: federal court | Statement: [Kellie Miller, legalActionIn, federal court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalActionIn Context triple: [Kellie Miller, legalActionIn, federal court]
-
A.
legalActionReason
Indicates the reason, cause, or grounds for which a particular legal action is initiated or taken.
-
B.
legalAct
Indicates that an entity performs, enacts, or is involved in a formal legal action, measure, or proceeding under a legal framework.
-
C.
legalActionFiled
chosen
Indicates that a formal legal proceeding or complaint has been officially initiated with the appropriate authority or court.
-
D.
legalProtectionFor
Indicates that one entity provides or is subject to legal safeguards, rights, or defenses in favor of another entity or interest.
-
E.
legalMatters
Indicates that one entity is involved with, concerned about, or responsible for legal issues, processes, or obligations related to another entity 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4f2a38c8190a682d8dae1ab9415 |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.