Triple
T15290034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hel |
E365501
|
entity |
| Predicate | demandsFromGods |
P6501
|
FINISHED |
| Object | tears from all things for Baldr’s release |
—
|
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: tears from all things for Baldr’s release | Statement: [Hel, demandsFromGods, tears from all things for Baldr’s release]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demandsFromGods Context triple: [Hel, demandsFromGods, tears from all things for Baldr’s release]
-
A.
demands
Indicates that one entity insists that another entity provide something or take a specific action, typically with authority or urgency.
-
B.
missionFromGod
Indicates that an entity is carrying out a task or purpose believed to be assigned or authorized by a divine being.
-
C.
appliesToDeityIn
Indicates that something (such as a rule, attribute, or statement) is relevant or applicable to a deity within a specified context or domain.
-
D.
demanded
chosen
Indicates that one entity forcefully or insistently requested something from another entity.
-
E.
involvesDeity
Indicates that the situation, event, or concept has the participation, presence, or relevance of a deity as a central element of the 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00e5635b4819092a69b5806d15bff |
completed | April 15, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:15 a.m.