Triple
T15600908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bilröst |
E375028
|
entity |
| Predicate | hasCosmicRole |
P59362
|
FINISHED |
| Object | supports travel of gods between realms |
—
|
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: supports travel of gods between realms | Statement: [Bilröst, hasCosmicRole, supports travel of gods between realms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCosmicRole Context triple: [Bilröst, hasCosmicRole, supports travel of gods between realms]
-
A.
hasInUniverseRole
Indicates that an entity holds or performs a specific role or function within a particular fictional or defined universe.
-
B.
roleInCosmos
chosen
Indicates the function, position, or significance an entity holds within the larger structure or order of the cosmos.
-
C.
cosmologicalRoleOf
Indicates the role or function an entity plays within a cosmological framework or system.
-
D.
hasCapitalRole
Indicates that an entity holds an official role, function, or status specifically associated with a capital city.
-
E.
cosmicFunction
Indicates a relationship where an entity serves a fundamental or overarching role within a cosmic or universal system.
- 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_69d85cce25008190b13b52745fbd719b |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e621fc4819097e8e85e7ddfdc6c |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:12 a.m.