Triple
T14400746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fólkvangr |
E357061
|
entity |
| Predicate | hasHallFunction |
P114096
|
FINISHED |
| Object | Sessrúmnir as Freyja's hall for the dead |
—
|
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: Sessrúmnir as Freyja's hall for the dead | Statement: [Fólkvangr, hasHallFunction, Sessrúmnir as Freyja's hall for the dead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHallFunction Context triple: [Fólkvangr, hasHallFunction, Sessrúmnir as Freyja's hall for the dead]
-
A.
hasTicketHall
Indicates that a place or facility includes or is equipped with a designated ticket hall area for purchasing or validating tickets.
-
B.
hasSingleHall
Indicates that an entity possesses exactly one hall within its structure or domain.
-
C.
hasExperimentalHall
Indicates that an entity possesses or includes an experimental hall as part of its facilities or structure.
-
D.
hadFunction
Indicates that an entity previously served or fulfilled a particular role, purpose, or function.
-
E.
hasLectureHall
Indicates that an entity possesses, includes, or is associated with a lecture hall as part of its facilities or structure.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de908500048190bb6a20fe318d5c62 |
completed | April 14, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
| PDg | Predicate description generation | batch_69de2e08b6c08190bb4c929deab236a6 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:17 a.m.