Triple
T14688600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The North Remembers |
E344977
|
entity |
| Predicate | hasMotifRelation |
P31989
|
FINISHED |
| Object | House Stark musical themes |
—
|
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: House Stark musical themes | Statement: [The North Remembers, hasMotifRelation, House Stark musical themes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMotifRelation Context triple: [The North Remembers, hasMotifRelation, House Stark musical themes]
-
A.
usesMotifsFrom
chosen
Indicates that one entity incorporates or draws upon recurring themes, patterns, or elements that originate from another entity.
-
B.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
-
C.
featuresMotif
Indicates that something contains, incorporates, or prominently includes a particular recurring motif or pattern.
-
D.
hasMotiveElement
Indicates that one entity includes, specifies, or is characterized by a particular motive-related component or factor in a broader relationship or action.
-
E.
sharesMotifsWith
Indicates that two entities contain or employ similar recurring themes, patterns, or symbolic elements.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb5844de481908a796eaa474bfde9 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.