Triple
T32082442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cerealia |
E819335
|
entity |
| Predicate | patronGoddess |
P56384
|
FINISHED |
| Object | Ceres |
—
|
NE NERFINISHED |
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: Ceres | Statement: [Cerealia, patronGoddess, Ceres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patronGoddess Context triple: [Cerealia, patronGoddess, Ceres]
-
A.
patronDeityOf
Indicates that one entity serves as the protective or primary deity associated with, worshipped by, or presiding over another entity (such as a person, group, or place).
-
B.
spiritualPatron
Indicates that one entity serves as a guiding or protective spiritual figure or patron for another entity.
-
C.
chosenGoddess
chosen
Indicates that a particular goddess has been selected or designated, typically as a preferred, patron, or special deity in relation to an entity.
-
D.
patroness
Indicates that a female person supports, sponsors, or acts as a benefactor for someone or something.
-
E.
associatedGoddess
Indicates that one entity is recognized as the goddess traditionally linked or connected to another entity (such as a place, concept, or deity).
- 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b580c3e481909f45d1716cde89ad |
completed | May 3, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:24 a.m.