Triple
T1060968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eleusis |
E22904
|
entity |
| Predicate | finalSuppressionOfCult |
P24356
|
FINISHED |
| Object | Late 4th century CE |
—
|
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: Late 4th century CE | Statement: [Eleusis, finalSuppressionOfCult, Late 4th century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalSuppressionOfCult Context triple: [Eleusis, finalSuppressionOfCult, Late 4th century CE]
-
A.
religionMinority
Indicates that the subject’s religion is a minority faith within the relevant population or context.
-
B.
ethnicReligion
Indicates that a religion is closely associated with a particular ethnic group, often tied to that group’s culture, ancestry, or identity.
-
C.
denominations
Indicates the specific units or categories into which something (often money, values, or items) is divided or classified.
-
D.
laterReligion
Indicates that one religion or religious affiliation chronologically follows or replaces another for the same entity.
-
E.
religiousReception
Indicates a relationship where one entity formally receives, welcomes, or hosts another in a specifically religious or faith-based context.
- F. None of above. chosen
Provenance (4 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4ba6e35ac8190802341c31bda0e3b |
completed | March 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69a4b7340a048190807363f19d17a58f |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4ba6d44c08190bf0ab28661ed8ca0 |
completed | March 1, 2026, 10:15 p.m. |
Created at: March 1, 2026, 7:42 p.m.