Triple
T3547455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfheim |
E75029
|
entity |
| Predicate | cosmicPosition |
P20412
|
FINISHED |
| Object | one of the upper worlds |
—
|
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: one of the upper worlds | Statement: [Alfheim, cosmicPosition, one of the upper worlds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cosmicPosition Context triple: [Alfheim, cosmicPosition, one of the upper worlds]
-
A.
positionInCosmogony
chosen
Indicates the role or place an entity occupies within a culture’s creation or origin narrative of the universe.
-
B.
celestialLocation
Indicates the spatial or positional relationship of an entity relative to a celestial body or region in space.
-
C.
cosmologicalSystem
Indicates a relationship in which entities are organized or interact as part of a larger cosmological structure or system (such as a universe, galaxy, or other large-scale cosmic arrangement).
-
D.
cosmicForm
Indicates a relationship where an entity manifests, assumes, or is represented in a vast, universal, or transcendent cosmic form.
-
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_69ad85d33c6c819081d5ac1df13b5680 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbfd0eb6081908f1380db4cfade87 |
completed | March 8, 2026, 6:28 p.m. |
| PD | Predicate disambiguation | batch_69adb83270ac819083967db0570167d2 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:20 p.m.