Triple
T35119059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varys |
E1014117
|
entity |
| Predicate | conspiresFor |
P6701
|
FINISHED |
| Object | restoration of House Targaryen (books) |
—
|
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: restoration of House Targaryen (books) | Statement: [Varys, conspiresFor, restoration of House Targaryen (books)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conspiresFor Context triple: [Varys, conspiresFor, restoration of House Targaryen (books)]
-
A.
conspirator
chosen
Indicates that an entity participates with others in planning or carrying out a secret or illicit scheme or action.
-
B.
conspiracy
Indicates a secret agreement or collaboration between multiple entities to plan or carry out an unlawful, deceptive, or harmful act.
-
C.
conspiracyType
Indicates the specific category or nature of a conspiracy associated with an entity or event.
-
D.
deathConspiracy
Indicates a relationship where one party is involved in planning, supporting, or believing in a covert plot to cause another party’s death.
-
E.
metConspiratorsAt
Indicates that an individual met with one or more co-conspirators at a specific place and/or time as part of a conspiracy.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.