Triple
T15552688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aesir at Ragnarök |
E370790
|
entity |
| Predicate | facesOpponent |
P18497
|
FINISHED |
| Object | jötunn |
—
|
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: jötunn | Statement: [Aesir at Ragnarök, facesOpponent, jötunn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facesOpponent Context triple: [Aesir at Ragnarök, facesOpponent, jötunn]
-
A.
facedOpponent
chosen
Indicates that one entity directly confronted or competed against another as an opponent in a contest, conflict, or challenge.
-
B.
associatedOpponent
Indicates that one entity is recognized or designated as an opponent or adversary associated with another entity in a given context.
-
C.
opponentInCase
Indicates that two parties are on opposing sides in the same legal case or proceeding.
-
D.
opponentSupporters
Indicates that the related entities are supporters or backers of opposing sides in a contest, conflict, or competition.
-
E.
wasOpponentOf
Indicates that one entity competed or conflicted against another as an adversary in some contest, game, or confrontation.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04a9551288190a583e8291c35f521 |
completed | April 16, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69deda7e6e748190b29ccce23298afef |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:08 a.m.