Triple
T29093326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parker v. District of Columbia (2007) |
E734919
|
entity |
| Predicate | wasAffirmedAsToResultIn |
P3106
|
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), wasAffirmedAsToResultIn, District of Columbia v. Heller]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasAffirmedAsToResultIn Context triple: [Parker v. District of Columbia (2007), wasAffirmedAsToResultIn, District of Columbia v. Heller]
-
A.
affirms
chosen
Indicates that one entity explicitly confirms, supports, or asserts the truth or validity of another entity, statement, or proposition.
-
B.
wasDecidedBy
Indicates that a decision or outcome was determined or resolved by a specific agent or authority.
-
C.
decidedIn
Indicates that a decision, ruling, or outcome was made within a particular case, proceeding, or deliberative context.
-
D.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
E.
decidedWith
Indicates that an entity made a decision jointly or in agreement with another entity.
- 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_69f6617f43748190b4880e1da320cdaa |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:06 a.m.