Triple
T14688676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The North |
E344978
|
entity |
| Predicate | defensiveConcern |
P115341
|
FINISHED |
| Object | threats beyond the Wall |
—
|
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: threats beyond the Wall | Statement: [The North, defensiveConcern, threats beyond the Wall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defensiveConcern Context triple: [The North, defensiveConcern, threats beyond the Wall]
-
A.
defensivePlan
Indicates a relationship where an entity formulates or adopts a strategy specifically intended to protect against threats, attacks, or other adverse actions.
-
B.
defensiveTask
Indicates a task in which an entity protects, guards, or defends another entity or resource from potential threats or harm.
-
C.
defensiveTactics
Indicates the use or implementation of strategies, maneuvers, or methods intended to protect, guard, or defend against threats or attacks.
-
D.
defensiveSystem
Indicates a system or mechanism whose primary function is to protect, guard, or defend an entity against threats or attacks.
-
E.
defensiveSkillEmphasized
Indicates that particular focus or priority is placed on developing or utilizing defensive skills in the relevant context.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69de716d3aac8190aaa6dc1f099b86e8 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:28 a.m.