Triple
T30107364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Festivals |
E765167
|
entity |
| Predicate | involvesDeities |
P16947
|
FINISHED |
| Object | Jupiter |
—
|
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: Jupiter | Statement: [The Festivals, involvesDeities, Jupiter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesDeities Context triple: [The Festivals, involvesDeities, Jupiter]
-
A.
involvesDeity
chosen
Indicates that the situation, event, or concept has the participation, presence, or relevance of a deity as a central element of the relationship.
-
B.
hasDeities
Indicates that one entity possesses, is associated with, or is served by one or more deities.
-
C.
coreDeitiesInvoked
Indicates that the primary or central deities of a tradition are explicitly called upon, referenced, or appealed to in a given context or act.
-
D.
discussesDeity
Indicates that one entity talks or writes about, analyzes, or otherwise engages in discourse concerning a deity or divine being.
-
E.
appliesToDeityIn
Indicates that something (such as a rule, attribute, or statement) is relevant or applicable to a deity within a specified context or domain.
- 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: April 29, 2026, 7:09 p.m.