Triple
T15041782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hymir |
E378615
|
entity |
| Predicate | testOrChallenge |
P106024
|
FINISHED |
| Object | requires Thor to break a goblet against his skull |
—
|
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: requires Thor to break a goblet against his skull | Statement: [Hymir, testOrChallenge, requires Thor to break a goblet against his skull]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testOrChallenge Context triple: [Hymir, testOrChallenge, requires Thor to break a goblet against his skull]
-
A.
challengeType
Indicates the specific category or kind of challenge associated with an action or relationship between entities.
-
B.
hasChallenge
Indicates that an entity faces, experiences, or is confronted with a particular difficulty, obstacle, or problem.
-
C.
test
chosen
Indicates that an entity performs, undergoes, or is associated with a testing or examination process involving another entity or condition.
-
D.
usedToChallenge
Indicates that one entity was employed or relied upon by another as a means to confront, contest, or question something or someone.
-
E.
mayBeChallengedBy
Indicates that one entity is allowed or able to be opposed, questioned, or contested by another entity.
- 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded82f73208190bb55fa6b20074e27 |
completed | April 15, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69de9a69d7848190b2b4662dd30f20e9 |
completed | April 14, 2026, 7:50 p.m. |
Created at: April 10, 2026, 3 a.m.