Triple
T34161720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odin’s throne room |
E876293
|
entity |
| Predicate | secondaryOccupant |
P157172
|
FINISHED |
| Object | Frigg |
—
|
NE NERFINISHED |
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: Frigg | Statement: [Odin’s throne room, secondaryOccupant, Frigg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryOccupant Context triple: [Odin’s throne room, secondaryOccupant, Frigg]
-
A.
hasSecondaryOccupant
chosen
Indicates that an entity has an additional, non-primary occupant associated with it.
-
B.
intendedOccupant
Indicates that one entity is designated or meant to be the occupant of another entity (such as a space, seat, or dwelling).
-
C.
secondaryPassengerProfile
Indicates that an entity serves as an additional or non-primary passenger associated with a main travel booking or passenger profile.
-
D.
laterOccupant
Indicates that one entity occupied or held a position in a place or role after another entity had previously done so.
-
E.
secondaryParticipants
Indicates that certain entities participate in an event or activity in a supporting or non-primary role alongside the main participants.
- 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69feff70fbec8190b1ff5f943f29613e |
completed | May 9, 2026, 9:33 a.m. |
| PD | Predicate disambiguation | batch_69fefbcd5b7881909cfe52b32f8a4301 |
completed | May 9, 2026, 9:18 a.m. |
Created at: May 1, 2026, 1:54 a.m.