Triple
T226692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Obergefell v. Hodges |
E4328
|
entity |
| Predicate | lowerCourtDecision |
P2931
|
FINISHED |
| Object | upheld state bans on same-sex marriage |
—
|
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: upheld state bans on same-sex marriage | Statement: [Obergefell v. Hodges, lowerCourtDecision, upheld state bans on same-sex marriage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerCourtDecision Context triple: [Obergefell v. Hodges, lowerCourtDecision, upheld state bans on same-sex marriage]
-
A.
lowerCourt
Indicates that one court holds a subordinate or inferior position in the judicial hierarchy relative to another court.
-
B.
hasLowerCourt
Indicates that one court functions as a subordinate or inferior court within the judicial hierarchy of another court.
-
C.
legalOutcome
chosen
Indicates the resulting legal status, decision, or consequence that follows from a legal process, action, or judgment.
-
D.
usedCourt
Indicates that an entity made use of or participated in legal proceedings within a particular court.
-
E.
chiefJusticeAtDecision
Indicates that the specified person was serving as the chief justice at the time a particular decision was made.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25d10ac248190a98dedabf5358668 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b5877588190af694d060377f027 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.