Triple
T29093329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parker v. District of Columbia (2007) |
E734919
|
entity |
| Predicate | hasSubsequentCaseName |
P67498
|
FINISHED |
| Object | District of Columbia v. Heller |
—
|
NE NERFINISHED |
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: District of Columbia v. Heller | Statement: [Parker v. District of Columbia (2007), hasSubsequentCaseName, District of Columbia v. Heller]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubsequentCaseName Context triple: [Parker v. District of Columbia (2007), hasSubsequentCaseName, District of Columbia v. Heller]
-
A.
subsequentCase
chosen
Indicates that one legal case follows another in time or procedural order, often relying on or referencing the earlier case.
-
B.
hasSubsequent
Indicates that one entity occurs, appears, or is positioned after another in a defined sequence or order.
-
C.
hasLegalPrecedentName
Indicates that a legal case, decision, or precedent is associated with a specific formal name or citation title.
-
D.
hasSuccessorBodyName
Indicates that one body is immediately followed or replaced by another body, identifying the name of its successor in a sequence or lineage.
-
E.
hasSubsequentNameChange
Indicates that an entity undergoes a later change to its name, resulting in a new official designation after the original.
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: April 28, 2026, 11:06 a.m.