Triple
T17556984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khepri |
E427613
|
entity |
| Predicate | solarCycleRole |
P97348
|
FINISHED |
| Object | morning form of the sun |
—
|
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: morning form of the sun | Statement: [Khepri, solarCycleRole, morning form of the sun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: solarCycleRole Context triple: [Khepri, solarCycleRole, morning form of the sun]
-
A.
solarCultRole
Indicates a role or function that an entity holds within a solar-focused religious cult or worship tradition.
-
B.
solarAlignment
Indicates that one entity is oriented, positioned, or timed in a specific way relative to the Sun’s location or movement.
-
C.
timeCycleRole
chosen
Indicates a role or function that an entity plays within a recurring or cyclical time pattern (such as a specific position or duty in a repeated time cycle).
-
D.
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).
-
E.
sunType
Indicates the classification relationship specifying what type or category of sun (or star) an entity is associated with.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4562357b48190bde6f49df0c983c2 |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.