Triple
T14781141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle at the Wall |
E347390
|
entity |
| Predicate | featuresCharacter |
P626
|
FINISHED |
| Object | Pyp |
E1119045
|
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: Pyp | Statement: [Battle at the Wall, featuresCharacter, Pyp]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pyp Context triple: [Battle at the Wall, featuresCharacter, Pyp]
-
A.
Pyp
chosen
Pyp is a member of the Night's Watch in the "A Song of Ice and Fire" novels and the "Game of Thrones" television series, known for his wit and close friendship with Jon Snow and Samwell Tarly.
-
B.
PY
PY is the two-letter ISO 3166-1 alpha-2 country code assigned to Paraguay.
-
C.
Pym
Pym is an English surname most notably associated with John Pym, a leading parliamentary figure in the early stages of the English Civil War.
-
D.
Pyr
Pyr is a science fiction and fantasy publishing imprint known for releasing speculative fiction titles under the Prometheus Books umbrella.
-
E.
PYG
PYG is the National Rail station code for Paisley Gilmour Street, a major railway station in Paisley, Scotland.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deca9de3f48190b7706925e2947cf5 |
completed | April 14, 2026, 11:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe24b626c48190a6aa9eda43539246 |
completed | May 8, 2026, 6 p.m. |
Created at: April 10, 2026, 1:31 a.m.