Triple
T14780182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shae |
E347369
|
entity |
| Predicate | relationshipTypeWith Tyrion Lannister |
P38921
|
FINISHED |
| Object | mistress |
—
|
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: mistress | Statement: [Shae, relationshipTypeWith Tyrion Lannister, mistress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipTypeWith Tyrion Lannister Context triple: [Shae, relationshipTypeWith Tyrion Lannister, mistress]
-
A.
relationshipType
Indicates the specific kind of relationship that exists between two or more entities.
-
B.
relationTypeToHenryVIII
Indicates the specific type of relationship an entity has to Henry VIII (e.g., familial, political, or social connection).
-
C.
relationshipToCharacter
chosen
Indicates the specific type of personal, social, or narrative connection that one entity has to a given character.
-
D.
showsRelationshipWith
Indicates that one entity visually or explicitly presents or demonstrates its connection or association with another entity.
-
E.
relationshipToTony
Indicates the specific type of relationship or connection that an entity has with Tony.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deca9c7cac8190ba900df95e42e318 |
completed | April 14, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.