Triple
T29843344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ram Chrysomallos |
E757859
|
entity |
| Predicate | offeredToDeity |
P190052
|
FINISHED |
| Object | Zeus |
—
|
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: Zeus | Statement: [Ram Chrysomallos, offeredToDeity, Zeus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredToDeity Context triple: [Ram Chrysomallos, offeredToDeity, Zeus]
-
A.
isOftenOfferedToDeity
Indicates that something is frequently presented or dedicated as an offering to a deity.
-
B.
appliesToDeityIn
Indicates that something (such as a rule, attribute, or statement) is relevant or applicable to a deity within a specified context or domain.
-
C.
offeredSacrificeOn
Indicates that one entity performed a sacrificial offering upon or at another entity (such as an altar, location, or occasion).
-
D.
servedDeity
Indicates that one entity acted in service, devotion, or worship toward a particular deity.
-
E.
hasVotiveOfferings
Indicates that an entity possesses or is associated with votive offerings dedicated or presented in a religious or ritual context.
- F. None of above. chosen
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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fcab6d41a88190a3576b4b088dcabd |
completed | May 7, 2026, 3:10 p.m. |
Created at: April 29, 2026, 5:40 p.m.