Triple
T3361375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Game of Thrones season 6 |
E70727
|
entity |
| Predicate | notablePlotEvent |
P259
|
FINISHED |
| Object | Jon Snow is resurrected |
—
|
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: Jon Snow is resurrected | Statement: [Game of Thrones season 6, notablePlotEvent, Jon Snow is resurrected]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlotEvent Context triple: [Game of Thrones season 6, notablePlotEvent, Jon Snow is resurrected]
-
A.
notableEventDate
Indicates the date on which a notable or significant event associated with the subject occurred.
-
B.
notableEventResponse
Indicates a response, reaction, or consequence that occurs as a result of a notable event.
-
C.
significantEvent
chosen
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
D.
famousForEvent
Indicates that an entity is widely known or recognized specifically because of a particular event.
-
E.
significantEventEnd
Indicates the point in time when a significant event or occurrence comes to a close or is considered finished.
- 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_69ad85a660c48190998489309a3b4869 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb26906948190851a7b7d543a4d64 |
completed | March 8, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69ada4317e288190ab7d0f66e9dba65f |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.