Triple
T18196011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eileithyia Cave near Heraklion |
E435663
|
entity |
| Predicate | primaryCultFunction |
P93071
|
FINISHED |
| Object | worship of a childbirth goddess |
—
|
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: worship of a childbirth goddess | Statement: [Eileithyia Cave near Heraklion, primaryCultFunction, worship of a childbirth goddess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCultFunction Context triple: [Eileithyia Cave near Heraklion, primaryCultFunction, worship of a childbirth goddess]
-
A.
primaryFunctionInPrehistory
Indicates the main role or use an entity had during prehistoric times, before written records.
-
B.
primaryFunctionInAntiquity
chosen
Indicates the main role or purpose an entity served during ancient times.
-
C.
primaryFunctionInLore
Indicates that something’s main role or purpose is defined within a fictional or narrative lore context.
-
D.
primaryServes
Indicates that one entity’s main or principal function is to serve, support, or provide service to another entity.
-
E.
primaryHeir
Indicates that one entity is the main or principal inheritor of another entity’s estate, title, or rights.
- 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e0d2ad5881909d846f3851ac9ec9 |
completed | April 19, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.