Triple
T31741179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rape of Ammu |
E810144
|
entity |
| Predicate | actualConsent |
P171316
|
FINISHED |
| Object | consensual relationship |
—
|
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: consensual relationship | Statement: [Rape of Ammu, actualConsent, consensual relationship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actualConsent Context triple: [Rape of Ammu, actualConsent, consensual relationship]
-
A.
hasGivenConsentFor
chosen
Indicates that one entity has granted permission or approval for a specific action, process, or use involving another entity or resource.
-
B.
laterConsentsTo
Indicates that one entity gives consent to another entity at a time subsequent to an earlier relevant event or point in the interaction.
-
C.
consentType
Indicates the specific kind or category of consent that has been given, requested, or recorded in the relationship.
-
D.
consentAuthority
Indicates that one entity has the legal or formal authority to give, withhold, or manage consent on behalf of another entity or for a particular action or process.
-
E.
consentTypeRequired
Indicates that a specific type or category of consent is required for the associated action or relationship to proceed.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ab4924cc81909046f5cc06c146bf |
completed | May 3, 2026, 1:56 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:25 p.m.