Triple
T37369149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oath of the Men of the Mountains to Isildur |
E927789
|
entity |
| Predicate | swornToOppose |
P437
|
FINISHED |
| Object | Sauron |
—
|
NE NERFINISHED |
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 | Statement: [Oath of the Men of the Mountains to Isildur, swornToOppose, Sauron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: swornToOppose Context triple: [Oath of the Men of the Mountains to Isildur, swornToOppose, Sauron]
-
A.
designedToOppose
Indicates that one entity is intentionally created or configured to counteract, resist, or work against another entity or process.
-
B.
opposedBy
chosen
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
C.
ledAgainst
Indicates that one entity directed or commanded an opposing effort, campaign, or force against another entity.
-
D.
canOppose
Indicates that one entity has the ability or capacity to resist, counteract, or act in opposition to another entity or its actions.
-
E.
opposedDuring
Indicates that one entity actively resisted or was in conflict with another entity during a specified time period or event.
- F. None of above.
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_69f76eb820248190a5c395ca50ad002a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:16 p.m.