Triple
T36557791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wainriders |
E901740
|
entity |
| Predicate | opponentInBattleOfTheCamp |
P18835
|
FINISHED |
| Object | King Calimehtar of Gondor |
—
|
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: King Calimehtar of Gondor | Statement: [Wainriders, opponentInBattleOfTheCamp, King Calimehtar of Gondor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentInBattleOfTheCamp Context triple: [Wainriders, opponentInBattleOfTheCamp, King Calimehtar of Gondor]
-
A.
battleOpponent
chosen
Indicates that two entities are engaged in or designated as opponents in a battle or combat scenario.
-
B.
opponentInScenario
Indicates that one entity is an adversary or rival of another within a specific scenario, context, or situation.
-
C.
partnerInBattle
Indicates that two entities are allied or cooperate as partners in the same battle or combat engagement.
-
D.
wasOpponentOf
Indicates that one entity competed or conflicted against another as an adversary in some contest, game, or confrontation.
-
E.
wasEnemyOf
Indicates that one entity regarded or interacted with another as an adversary or opponent, typically in a hostile or conflicting relationship.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:11 p.m.