Triple
T29078573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Themysciran |
E733910
|
entity |
| Predicate | notableDeitiesWorshipped |
P2291
|
FINISHED |
| Object | Hera |
E16933
|
NE 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: Hera | Statement: [Themysciran, notableDeitiesWorshipped, Hera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDeitiesWorshipped Context triple: [Themysciran, notableDeitiesWorshipped, Hera]
-
A.
worshippedDeityCulture
Indicates that a particular culture reveres, honors, or practices religious devotion toward a specific deity.
-
B.
veneratedBeings
Indicates that certain beings are regarded with deep respect, reverence, or worship by others.
-
C.
worshippedIn
chosen
Indicates that a particular deity, figure, or object of reverence is the focus of religious or spiritual worship within a specified place or context.
-
D.
hasDeities
Indicates that one entity possesses, is associated with, or is served by one or more deities.
-
E.
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).
- F. None of above.
Provenance (4 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a0224f4b6cc8190a8f79700a9af765f |
completed | May 11, 2026, 6:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a251f7dd1cc8190afd3072b8a76f9e5 |
completed | June 7, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_6a0223f01eb081909419518fdd45f2a4 |
completed | May 11, 2026, 6:46 p.m. |
Created at: April 28, 2026, 10:51 a.m.