Triple
T16097666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judge Joe Brown |
E390527
|
entity |
| Predicate | litigantStatus |
P121891
|
FINISHED |
| Object | non-actors |
—
|
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: non-actors | Statement: [Judge Joe Brown, litigantStatus, non-actors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: litigantStatus Context triple: [Judge Joe Brown, litigantStatus, non-actors]
-
A.
defendantStatus
Indicates the legal condition or standing of a defendant within a judicial or law-enforcement process.
-
B.
legalStatusOfProceedings
Indicates the current legal standing or condition of a set of legal proceedings within a judicial or administrative process.
-
C.
judicialStatus
Indicates the legal or court-related condition or standing of an entity within a judicial process (e.g., pending, decided, appealed).
-
D.
complainantStatus
Indicates the role or standing of the person or party making a complaint in relation to the case or issue.
-
E.
courtStatus
Indicates the current legal or procedural state of a case or matter within a court system.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff6551a48190afb7e0c61e22b541 |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e1ff5cd7e481908a29214139a3de2e |
completed | April 17, 2026, 9:37 a.m. |
Created at: April 10, 2026, 4:59 a.m.