Triple
T3284524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Winds of Winter |
E68947
|
entity |
| Predicate | anticipatedBy |
P786
|
FINISHED |
| Object | readers of A Song of Ice and Fire |
—
|
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: readers of A Song of Ice and Fire | Statement: [The Winds of Winter, anticipatedBy, readers of A Song of Ice and Fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: anticipatedBy Context triple: [The Winds of Winter, anticipatedBy, readers of A Song of Ice and Fire]
-
A.
anticipates
chosen
Indicates that one entity expects or predicts a future event, action, or state involving another entity before it actually occurs.
-
B.
wasPrecededBy
Indicates that one event, state, or entity occurred or existed earlier in time than another.
-
C.
heldBefore
Indicates that one entity possessed or maintained control of something at an earlier time than another entity or event.
-
D.
cededTo
Indicates that control, ownership, or authority over something was formally transferred from one entity to another.
-
E.
predictedIn
Indicates that something has been forecast, anticipated, or estimated to occur within or as part of a specified context, time, or situation.
- 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_69ad859c463481909ca4be267336c290 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0377c9c819089af47952946de52 |
completed | March 8, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69ada421fadc8190b7c7d3c8afd20061 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.