Triple
T37369177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oath of the Men of the Mountains to Isildur |
E927789
|
entity |
| Predicate | connectedToEnemy |
P195750
|
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, connectedToEnemy, Sauron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToEnemy Context triple: [Oath of the Men of the Mountains to Isildur, connectedToEnemy, Sauron]
-
A.
hasFriendEnemyRelationshipWith
Indicates a relationship where two entities are simultaneously connected as both friends and enemies, reflecting a mixed or ambivalent association between them.
-
B.
hasEnemies
chosen
Indicates that one entity is in an antagonistic or hostile relationship with another, considering them an enemy.
-
C.
enemyCharacterIn
Indicates that a character is located within or present inside an enemy-controlled area, zone, or context.
-
D.
enemyAtFirst
Indicates that two entities initially regard or treat each other as enemies when they first meet or interact.
-
E.
isInContactWith
Indicates that two entities are physically touching or directly connected so that contact between them is established.
- 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_69ffe12ee59c8190bc7da386e6d5332d |
completed | May 10, 2026, 1:36 a.m. |
| PD | Predicate disambiguation | batch_69ffe0a138bc8190a3d4b48cd579e985 |
completed | May 10, 2026, 1:34 a.m. |
Created at: May 3, 2026, 4:16 p.m.