Triple
T4512084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soma |
E102075
|
entity |
| Predicate | astralRole |
P52566
|
FINISHED |
| Object | lord of constellations |
—
|
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: lord of constellations | Statement: [Soma, astralRole, lord of constellations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: astralRole Context triple: [Soma, astralRole, lord of constellations]
-
A.
astronomicalRole
Indicates the functional or positional role that one astronomical object or entity has in relation to another (e.g., star vs. planet, primary vs. satellite).
-
B.
roleInConstellation
chosen
Indicates the specific function or position an entity holds within a particular constellation.
-
C.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
D.
roleInGalaxy
Indicates the specific function, status, or influence an entity holds within the broader structure or dynamics of a galaxy.
-
E.
fictionalUniverseRole
Indicates the role or function an entity has within a particular fictional universe or narrative setting.
- 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd571412788190a374abd1e05519e4 |
completed | March 20, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69bd5218afb4819087c99e0a1f22e137 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:01 p.m.