Triple
T14366644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balon Greyjoy |
E356251
|
entity |
| Predicate | seat |
P75
|
FINISHED |
| Object | Pyke |
E345006
|
NE 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: Pyke | Statement: [Balon Greyjoy, seat, Pyke]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pyke Context triple: [Balon Greyjoy, seat, Pyke]
-
A.
Pyke
chosen
Pyke is the rugged, storm-battered stronghold of House Greyjoy on the Iron Islands in the world of Westeros.
-
B.
Pyros
Pyros is a legendary Mage minion from Hearthstone that repeatedly returns to hand in increasingly powerful elemental forms each time it dies.
-
C.
Pyr
Pyr is a science fiction and fantasy publishing imprint known for releasing speculative fiction titles under the Prometheus Books umbrella.
-
D.
Pyro
"Pyro" is a song by American rock band Kings of Leon from their 2010 album *Come Around Sundown*.
-
E.
Pyro
Pyro is a fictional character best known as the flamethrowing arsonist class from the video game Team Fortress 2, characterized by a gas mask, muffled speech, and an ambiguous, unsettling personality.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8faf00e8819087d7100e9d8c1877 |
completed | April 14, 2026, 7:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd4c4fa3788190b7fa5c34620c3ada |
completed | May 8, 2026, 2:37 a.m. |
Created at: April 10, 2026, 1:15 a.m.