Triple
T3250661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Game of Thrones season 1 |
E68167
|
entity |
| Predicate | notableEventInPlot |
P7326
|
FINISHED |
| Object | execution of Eddard Stark |
—
|
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: execution of Eddard Stark | Statement: [Game of Thrones season 1, notableEventInPlot, execution of Eddard Stark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEventInPlot Context triple: [Game of Thrones season 1, notableEventInPlot, execution of Eddard Stark]
-
A.
notableStoryArc
Indicates that there exists a significant or prominent narrative storyline or plot development involving the subject.
-
B.
notableScene
chosen
Indicates that a particular scene is especially significant, memorable, or noteworthy within a work or context.
-
C.
notableEventResponse
Indicates a response, reaction, or consequence that occurs as a result of a notable event.
-
D.
notableStory
Indicates that an entity is the subject or source of a story, account, or narrative that is considered notable or significant.
-
E.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
- 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_69ad858e4c708190aa31d486cfee8a6a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf40f7908190a450c3136fccb020 |
completed | March 8, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69ada41837e48190933572165be0ca38 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.