Triple
T60880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roe v. Wade |
E1209
|
entity |
| Predicate | hasDecisionDate |
P2232
|
FINISHED |
| Object | 1973-01-22 |
—
|
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: 1973-01-22 | Statement: [Roe v. Wade, hasDecisionDate, 1973-01-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDecisionDate Context triple: [Roe v. Wade, hasDecisionDate, 1973-01-22]
-
A.
decisionDate
chosen
Indicates the date on which a specific decision was formally made or finalized.
-
B.
yearDecided
Indicates the specific calendar year in which a decision, ruling, or resolution was formally made or finalized.
-
C.
decidesOn
Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
-
D.
concludedAt
Indicates the point in time at which an event, process, or relationship comes to an end or is completed.
-
E.
associatedWithDecision
Indicates a relationship where an entity is linked or connected to a particular decision, such that the decision is relevant to, influenced by, or otherwise tied to that 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a251a1b8ac8190b44be4c3c41e5681 |
completed | Feb. 28, 2026, 2:23 a.m. |
| PD | Predicate disambiguation | batch_69a24ea0bec48190b2af1fb287e9e692 |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.