Triple
T6924500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chalkeia |
E160270
|
entity |
| Predicate | linkedDeityCult |
P26045
|
FINISHED |
| Object | cult of Athena |
—
|
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: cult of Athena | Statement: [Chalkeia, linkedDeityCult, cult of Athena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedDeityCult Context triple: [Chalkeia, linkedDeityCult, cult of Athena]
-
A.
sharesDeitiesWith
Indicates that two entities have one or more deities in common within their respective religious or mythological systems.
-
B.
associatedCult
chosen
Indicates that an entity is connected or linked to a particular cult, typically through membership, affiliation, or influence.
-
C.
relationshipToDeities
Indicates how an entity is connected or related to one or more deities, such as through worship, lineage, role, or status.
-
D.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
E.
integratesDeity
Indicates that one entity incorporates, assimilates, or unifies a deity or divine aspect into itself or into a larger system.
- 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_69c6884d350081908d8a970e4d40ad78 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9fea8d08190b6099a24fbac7de5 |
completed | March 27, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bb577c81908ee8b415b4281f3d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:26 p.m.