Triple
T29036987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Apollo Epicurius |
E737887
|
entity |
| Predicate | epithetOfDeity |
P124236
|
FINISHED |
| Object | Epicurius |
—
|
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: Epicurius | Statement: [Temple of Apollo Epicurius, epithetOfDeity, Epicurius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: epithetOfDeity Context triple: [Temple of Apollo Epicurius, epithetOfDeity, Epicurius]
-
A.
epithetOfPantheon
Indicates that one term is used as an epithet or honorific title specifically for a deity or figure within a particular pantheon.
-
B.
hasCultEpithetOfDeity
chosen
Indicates that a specific cult epithet or title is associated with, or used for, a particular deity.
-
C.
attributeOfDeity
Indicates that something is a characteristic, quality, or property belonging to a deity.
-
D.
epithetAppliedBy
Indicates that a particular epithet or descriptive label is used or assigned by a specific agent to a target entity.
-
E.
epithetOrTitle
Indicates that one entity serves as an epithet, honorific, or formal title used to designate or characterize another entity.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6603db2988190af8ce0beaaec257d |
completed | May 2, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:59 a.m.