Triple
T4249098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyrenaikē |
E95800
|
entity |
| Predicate | earlierDominantReligion |
P111
|
FINISHED |
| Object | ancient Greek religion |
—
|
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: ancient Greek religion | Statement: [Kyrenaikē, earlierDominantReligion, ancient Greek religion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierDominantReligion Context triple: [Kyrenaikē, earlierDominantReligion, ancient Greek religion]
-
A.
dominantReligionLegacy
Indicates that a historically dominant religion has left a lasting influence or heritage on a society, culture, or region.
-
B.
dominantReligion
Indicates the religion that holds primary or majority status within a given group, region, or entity.
-
C.
previousReligionOfKingdom
Indicates that a specified religion was formerly practiced or officially adopted by a kingdom before being replaced or superseded.
-
D.
formerReligiousAffiliation
chosen
Indicates that an entity previously adhered to a particular religion or religious denomination but no longer does so.
-
E.
foundedReligion
Indicates that an entity established or originated a particular religion.
- 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_69b3453f759881909b91f01a1e82c036 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e9df10881908a2f039773f8afaa |
completed | March 12, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69b347f73e008190a908a48ef389945a |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:06 p.m.