Triple
T38240838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nymeria |
E1013754
|
entity |
| Predicate | TVNotableEpisode |
P2757
|
FINISHED |
| Object | Game of Thrones S7E2 "Stormborn" |
—
|
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: Game of Thrones S7E2 "Stormborn" | Statement: [Nymeria, TVNotableEpisode, Game of Thrones S7E2 "Stormborn"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TVNotableEpisode Context triple: [Nymeria, TVNotableEpisode, Game of Thrones S7E2 "Stormborn"]
-
A.
notableEpisode
chosen
Indicates that a particular episode is especially significant, memorable, or noteworthy in relation to the subject.
-
B.
notableEpisodeEvent
Indicates that an event is especially significant or noteworthy within the context of a particular episode.
-
C.
notableEP
Indicates that an entity is especially well-known or significant for a particular EP (extended play recording).
-
D.
notableEpisodeTypes
Indicates that certain types or categories of episodes are especially significant or noteworthy in relation to the subject.
-
E.
notableShow
Indicates that a show is especially prominent, distinguished, or significant in some noteworthy way.
- 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_69f76dd72a248190a5fe18db2bd1eb15 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc3321ef081908023590ba70ba0cf |
completed | May 7, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fdc6e08190b05e894c59481a0d |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.