Triple
T15500033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thrym |
E378927
|
entity |
| Predicate | feastHeldFor |
P2302
|
FINISHED |
| Object | wedding with supposed Freyja |
—
|
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: wedding with supposed Freyja | Statement: [Thrym, feastHeldFor, wedding with supposed Freyja]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feastHeldFor Context triple: [Thrym, feastHeldFor, wedding with supposed Freyja]
-
A.
feastType
Indicates the specific kind or category of feast associated with an event or occasion.
-
B.
feast
chosen
Indicates that an entity participates in or hosts a large, elaborate meal or celebration involving abundant food and communal dining.
-
C.
feastFollows
Indicates that a feast or celebratory meal occurs after and as a consequence of a preceding event or action.
-
D.
feastTraditionalName
Indicates the traditional or customary name by which a particular feast or celebration is known.
-
E.
feastEstablishedBy
Indicates that a particular feast or celebratory event was created, instituted, or formally initiated by a specific agent or authority.
- 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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03fcb4e8c81908e4ab463e3ae252b |
completed | April 16, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:54 a.m.