Triple
T15393975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thor (as recipient of crafted items) |
E368120
|
entity |
| Predicate | artifactFunction |
P118615
|
FINISHED |
| Object | Mjölnir protects Asgard |
—
|
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: Mjölnir protects Asgard | Statement: [Thor (as recipient of crafted items), artifactFunction, Mjölnir protects Asgard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artifactFunction Context triple: [Thor (as recipient of crafted items), artifactFunction, Mjölnir protects Asgard]
-
A.
artisticFunction
Indicates that one entity serves a creative, expressive, or aesthetic role or purpose in relation to another entity.
-
B.
artifactType
Indicates the specific kind or category of artifact that an entity is classified as.
-
C.
artifact
Indicates that one entity is an artifact created, modified, or used by another entity.
-
D.
conceptualFunction
Indicates a relationship where one entity serves as an abstract or conceptual function that operates on, transforms, or maps another entity within a conceptual or theoretical framework.
-
E.
artUse
Indicates that one entity uses, applies, or employs another entity within an artistic or creative context.
- F. None of above. chosen
Provenance (4 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e7838b48190862b43c6c8620692 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:19 a.m.