Triple
T21917906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Megalesia |
E541227
|
entity |
| Predicate | connectedDeityAspect |
P102272
|
FINISHED |
| Object | mother goddess |
—
|
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: mother goddess | Statement: [Megalesia, connectedDeityAspect, mother goddess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedDeityAspect Context triple: [Megalesia, connectedDeityAspect, mother goddess]
-
A.
hasDeityAspect
Indicates that one entity embodies, represents, or functions as a specific divine aspect or manifestation of another deity.
-
B.
relationshipToDeities
Indicates how an entity is connected or related to one or more deities, such as through worship, lineage, role, or status.
-
C.
associatedDeityOrForce
chosen
Indicates that one entity is linked to, represented by, or under the influence of a particular deity or supernatural force.
-
D.
integratesDeity
Indicates that one entity incorporates, assimilates, or unifies a deity or divine aspect into itself or into a larger system.
-
E.
linkedTempleDeity
Indicates a relationship where a temple is associated with, or dedicated to, a particular 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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1233924008190923724d0c0f2d435 |
completed | April 28, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e6be9ebf4c8190892df1a8e1313f88 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:43 p.m.