Triple
T35118809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tysha |
E1014112
|
entity |
| Predicate | forcedToHaveSexWith |
P182572
|
FINISHED |
| Object | Lannister guards |
—
|
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: Lannister guards | Statement: [Tysha, forcedToHaveSexWith, Lannister guards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forcedToHaveSexWith Context triple: [Tysha, forcedToHaveSexWith, Lannister guards]
-
A.
makesUnwantedAdvancesToward
Indicates that one entity directs unwelcome or inappropriate romantic or sexual advances toward another entity.
-
B.
coneSex
Indicates a sexual or mating relationship involving a cone-shaped structure or entity.
-
C.
hasSex
Indicates that one entity engages in sexual activity with another entity.
-
D.
usedBeforeMarriageAs
Indicates that one entity was used by or associated with another entity prior to that entity’s marriage.
-
E.
hasAffairWith
Indicates that one entity is engaged in a secret or illicit romantic or sexual relationship with another entity, typically outside a committed partnership.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7904a770481908ef3f788e51e8dba |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78f629d508190b755848162c4e101 |
completed | May 3, 2026, 6:09 p.m. |
Created at: May 3, 2026, 4:01 p.m.