Triple
T18195889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilithyia |
E435659
|
entity |
| Predicate | associatedWithDeity |
P1481
|
FINISHED |
| Object | Apollo |
—
|
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: Apollo | Statement: [Ilithyia, associatedWithDeity, Apollo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Apollo Context triple: [Ilithyia, associatedWithDeity, Apollo]
-
A.
Apollo
Apollo is a small borough in Armstrong County, Pennsylvania, known historically as a riverfront industrial community along the Kiskiminetas River.
-
B.
Apollo
Apollo is a well-known brand that produces a range of bicycles and related cycling products.
-
C.
Apollo
chosen
Apollo is the Olympian god of the sun, music, prophecy, and healing in ancient Greek mythology.
-
D.
Apollo Clarios
Apollo Clarios is a local cult epithet of the god Apollo venerated at the ancient oracular sanctuary of Claros in Ionia, where he was worshipped primarily as a prophetic and healing deity.
-
E.
Apollo Daphnephoros
Apollo Daphnephoros is a cult epithet of the Greek god Apollo associated with laurel and often worshipped as a protector and guide, particularly in cities like Eretria.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e0d2ad5881909d846f3851ac9ec9 |
completed | April 19, 2026, 2:04 p.m. |
Created at: April 10, 2026, 10:31 a.m.