Triple
T28890741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gothmog (Lieutenant of Morgul) |
E732685
|
entity |
| Predicate | sideInWarOfTheRing |
P165493
|
FINISHED |
| Object | Sauron's side |
—
|
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: Sauron's side | Statement: [Gothmog (Lieutenant of Morgul), sideInWarOfTheRing, Sauron's side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideInWarOfTheRing Context triple: [Gothmog (Lieutenant of Morgul), sideInWarOfTheRing, Sauron's side]
-
A.
roleInWarOfTheRing
Indicates the specific function, position, or involvement an entity had within the events of the War of the Ring.
-
B.
roleInBattleOfFiveArmies
Indicates the specific function, position, or involvement an entity had in the Battle of Five Armies.
-
C.
statusAfterWarOfTheRing
Indicates the condition or role an entity has following the events of the War of the Ring.
-
D.
broughtToMiddleEarthBy
Indicates that one entity is the agent or means by which another entity was transported or introduced into Middle-earth.
-
E.
isShireSeatOf
Indicates that a location serves as the administrative center or county town (shire seat) for a given shire or county.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65a75dfc88190b919126bcafd64c7 |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 28, 2026, 7:55 a.m.