Triple
T35118818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tysha |
E1014112
|
entity |
| Predicate | truthRevealedIn |
P107569
|
FINISHED |
| Object | A Storm of Swords |
—
|
NE NERFINISHED |
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: A Storm of Swords | Statement: [Tysha, truthRevealedIn, A Storm of Swords]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: truthRevealedIn Context triple: [Tysha, truthRevealedIn, A Storm of Swords]
-
A.
triesToRevealTruthTo
Indicates an attempt by one entity to make another entity aware of what it believes to be the true facts or reality of a situation.
-
B.
revealedSecretOf
Indicates that one entity has disclosed or exposed confidential or previously unknown information belonging to another entity.
-
C.
secretRevealedThrough
chosen
Indicates that a secret becomes known or disclosed by means of a specified channel, method, or intermediary.
-
D.
secretRevealed
Indicates that previously hidden or confidential information has been disclosed to one or more parties.
-
E.
fullRevelation
Indicates that all relevant information, details, or aspects of something are completely disclosed or made fully known without omission.
- 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_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:01 p.m.