Triple
T36556202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eärnur |
E901704
|
entity |
| Predicate | actionAtFornost |
P185851
|
FINISHED |
| Object | pursued the Witch-king |
—
|
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: pursued the Witch-king | Statement: [Eärnur, actionAtFornost, pursued the Witch-king]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actionAtFornost Context triple: [Eärnur, actionAtFornost, pursued the Witch-king]
-
A.
actionAtRagnarök
Indicates an action or event that is specifically performed or occurs during Ragnarök, the final apocalyptic battle in Norse mythology.
-
B.
forcesAction
Indicates that one entity compels or coerces another entity to perform a specific action or behavior.
-
C.
FAAction
Indicates an action or operation performed by one entity that affects or involves another entity.
-
D.
mainFort
Indicates that one entity serves as the primary or central fortification associated with another entity.
-
E.
setsForth
Indicates that an entity formally presents, explains, or lays out something such as a plan, argument, rule, or proposal.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c3705b5c81908c84004543a71c07 |
completed | May 3, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:11 p.m.