Triple
T28736555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kubaba |
E730816
|
entity |
| Predicate | religiousContinuityWith |
P180842
|
FINISHED |
| Object | Cybele |
—
|
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: Cybele | Statement: [Kubaba, religiousContinuityWith, Cybele]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousContinuityWith Context triple: [Kubaba, religiousContinuityWith, Cybele]
-
A.
religiousCounterpart
chosen
Indicates that one entity serves as the religious equivalent or analogue of another entity within a different belief system or tradition.
-
B.
laterReligion
Indicates that one religion or religious affiliation chronologically follows or replaces another for the same entity.
-
C.
religiousEnvironment
Indicates the religious context, atmosphere, or setting in which an entity exists or an action takes place.
-
D.
religiousFoundation
Indicates that an entity was established, created, or founded by a religious organization, authority, or tradition.
-
E.
religiousSpectrum
Indicates a relationship that places entities along a range or continuum of religious belief, practice, or affiliation.
- 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: April 28, 2026, 6:01 a.m.