Triple
T14962385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great War against the dead |
E373093
|
entity |
| Predicate | goalOfLiving |
P116862
|
FINISHED |
| Object | prevent the Long Night |
—
|
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: prevent the Long Night | Statement: [Great War against the dead, goalOfLiving, prevent the Long Night]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalOfLiving Context triple: [Great War against the dead, goalOfLiving, prevent the Long Night]
-
A.
goals
Indicates that an entity has objectives, targets, or desired outcomes it aims to achieve.
-
B.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
-
C.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
D.
goalOfRevitalization
Indicates an effort or initiative aimed at restoring, renewing, or strengthening something that has declined or weakened.
-
E.
findsPurposeThrough
Indicates that one entity derives its sense of purpose, meaning, or fulfillment through its relationship with or actions involving another entity.
- 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6cece6881908cd8c8fe41583bee |
completed | April 15, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69de9a5d995881909e33658f5aea5582 |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:40 a.m.