Triple
T35118808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tysha |
E1014112
|
entity |
| Predicate | forcedProstitutionOrderedBy |
P120322
|
FINISHED |
| Object | Tywin Lannister |
E348460
|
NE 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: Tywin Lannister | Statement: [Tysha, forcedProstitutionOrderedBy, Tywin Lannister]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forcedProstitutionOrderedBy Context triple: [Tysha, forcedProstitutionOrderedBy, Tywin Lannister]
-
A.
abductionOrderedBy
Indicates that one entity has formally requested or directed the abduction of another entity.
-
B.
exploitedFor
chosen
Indicates that one entity is unfairly or abusively used by another entity as a resource, means, or advantage for the latter’s benefit.
-
C.
legalStatusOfProstitution
Indicates the legal status or regulatory condition under which prostitution is permitted, restricted, or prohibited in a given jurisdiction.
-
D.
courtOrdered
Indicates that an action, condition, or relationship exists because it has been formally mandated or imposed by a court order.
-
E.
committedCrime
Indicates that an entity has carried out or been responsible for a criminal act or offense.
- F. None of above.
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_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3803f6ff7c81908b9ae3e4b59c6c38 |
completed | June 21, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.