Triple
T21045002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louisiana district courts |
E518424
|
entity |
| Predicate | handlesPostJudgmentMotions |
P142597
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Louisiana district courts, handlesPostJudgmentMotions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesPostJudgmentMotions Context triple: [Louisiana district courts, handlesPostJudgmentMotions, true]
-
A.
judgmentInvolves
Indicates that a particular judgment, decision, or legal ruling includes, concerns, or pertains to a specified entity or matter.
-
B.
seeksJudgmentFrom
Indicates that one entity actively requests or pursues a formal decision, evaluation, or ruling from another entity.
-
C.
heldByCourt
Indicates that a particular legal position, opinion, or decision is asserted or determined by a court.
-
D.
movedCourtFrom
Indicates that an entity changed its legal venue or jurisdiction from one court to another.
-
E.
canAdjourn
Indicates that an entity has the authority or ability to formally end, suspend, or postpone a meeting, session, or proceeding.
- 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_69e0b50438e08190917e2538bb8bc034 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fcf2fc4881909b9e3400864e6b82 |
completed | April 21, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 2:30 p.m.