Triple
T3514663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jormungandr |
E74276
|
entity |
| Predicate | appearsInStory |
P795
|
FINISHED |
| Object | Thor’s fishing trip with Hymir |
—
|
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: Thor’s fishing trip with Hymir | Statement: [Jormungandr, appearsInStory, Thor’s fishing trip with Hymir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInStory Context triple: [Jormungandr, appearsInStory, Thor’s fishing trip with Hymir]
-
A.
appearsIn
chosen
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
B.
appearsInSeries
Indicates that an entity is featured or occurs within a particular series.
-
C.
positionInStory
Indicates the point or role an event, character, or element occupies within the overall sequence or structure of a story.
-
D.
appearsFor
Indicates that one entity is presented, shown, or made visible on behalf of, or in representation of, another entity.
-
E.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
- 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_69ad85cfb5c881909c9a2edd9d6043cc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc2efa4c8190ac1ca221f3f0eba4 |
completed | March 8, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69adae10689c8190b7dc6d7daa8295b6 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.