Triple
T3468347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olympus region (nearby) |
E73190
|
entity |
| Predicate | associatedDeityGroup |
P15725
|
FINISHED |
| Object | Olympian gods |
—
|
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: Olympian gods | Statement: [Olympus region (nearby), associatedDeityGroup, Olympian gods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedDeityGroup Context triple: [Olympus region (nearby), associatedDeityGroup, Olympian gods]
-
A.
hasDeityGroup
chosen
Indicates a relationship where an entity is associated with, or belongs to, a particular group or pantheon of deities.
-
B.
sharesDeitiesWith
Indicates that two entities have one or more deities in common within their respective religious or mythological systems.
-
C.
relatedNameOfGod
Indicates that one entity is a name, title, or designation that refers to or is associated with God.
-
D.
hasComponentDeity
Indicates that an entity (such as a religion, mythology, or pantheon) includes a particular deity as one of its constituent or associated divine figures.
-
E.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
- 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_69ad85b2fed48190948c8765e453d270 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb11ec5881908347bf92883a25ee |
completed | March 8, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69adae05bb0081909dc7e4779d6e05ef |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.