Triple
T3641311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bifrost |
E77192
|
entity |
| Predicate | realmTypeConnected |
P49969
|
FINISHED |
| Object | realm of gods |
—
|
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: realm of gods | Statement: [Bifrost, realmTypeConnected, realm of gods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realmTypeConnected Context triple: [Bifrost, realmTypeConnected, realm of gods]
-
A.
realmType
Indicates the classification or category of a realm, specifying what kind or type of realm it is.
-
B.
formerlyConnectedTo
Indicates that two entities were once connected or associated in some way, but that connection no longer exists.
-
C.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
D.
associatedWithRealm
Indicates a relationship where an entity is linked or connected to a particular realm, domain, or sphere of influence.
-
E.
realmWithin
Indicates that one realm or domain is contained inside, or exists as a subset of, another realm or domain.
- 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_69ad85de1b988190a45f8dbfebc806fc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc357c3308190bd8801d68244a53e |
completed | March 8, 2026, 6:43 p.m. |
| PD | Predicate disambiguation | batch_69adb8445b2c8190ab07f6ad4e010d0e |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb8e4ba948190a9b777cf7f788b96 |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:24 p.m.