Triple
T60918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roe v. Wade |
E1209
|
entity |
| Predicate | concernsRight |
P4517
|
FINISHED |
| Object | women’s reproductive autonomy |
—
|
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: women’s reproductive autonomy | Statement: [Roe v. Wade, concernsRight, women’s reproductive autonomy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concernsRight Context triple: [Roe v. Wade, concernsRight, women’s reproductive autonomy]
-
A.
issues
Indicates that an entity formally produces, releases, or distributes something, such as a document, order, or resource, making it officially available.
-
B.
remedySought
Indicates that a particular legal or corrective action is being requested as a solution or relief in response to a problem or dispute.
-
C.
recognizedRight
Indicates that an agent formally acknowledges and accepts that another party possesses a specific right or entitlement.
-
D.
ensures
Indicates that one entity guarantees or makes certain that a particular condition, outcome, or state holds for another entity or situation.
-
E.
involves
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
- 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_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. |
| PDg | Predicate description generation | batch_69a251a088f8819083797c2baf310c39 |
completed | Feb. 28, 2026, 2:23 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.