Triple
T31538543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gabrielle Darley |
E804676
|
entity |
| Predicate | rightsViolatedClaim |
P171947
|
FINISHED |
| Object | right to privacy |
—
|
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: right to privacy | Statement: [Gabrielle Darley, rightsViolatedClaim, right to privacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rightsViolatedClaim Context triple: [Gabrielle Darley, rightsViolatedClaim, right to privacy]
-
A.
rightsImplicated
Indicates that certain rights are affected, challenged, or brought into question as a consequence of the related action or relationship.
-
B.
claimedRight
Indicates that an entity asserts or demands a right or entitlement in relation to another entity or resource.
-
C.
rightsEnforced
Indicates that legal or moral rights are actively upheld, protected, or compelled through appropriate mechanisms or actions.
-
D.
typeOfClaim
Indicates the specific category or nature of a claim being made in relation to an entity or statement.
-
E.
claimsToDefend
Indicates that one entity asserts or professes that its actions or stance are intended to protect or uphold another entity or value.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a956e9b08190bf83547bba8e8147 |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:05 p.m.