Triple
T6241813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eucleia |
E139619
|
entity |
| Predicate | hasCultAspect |
P61308
|
FINISHED |
| Object | personification of good repute |
—
|
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: personification of good repute | Statement: [Eucleia, hasCultAspect, personification of good repute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCultAspect Context triple: [Eucleia, hasCultAspect, personification of good repute]
-
A.
hasCultFollowing
Indicates that something has attracted a small but highly dedicated and enthusiastic group of supporters or fans.
-
B.
hasMysteryCult
Indicates that an entity is associated with, participates in, or possesses a mystery cult, typically involving secret or esoteric religious practices.
-
C.
hasCultTitle
Indicates that an entity is known by or associated with a specific cult-related title or honorific.
-
D.
hasAssociatedCulture
Indicates that an entity is related to, influenced by, or characterized by a particular culture.
-
E.
cultAspect
chosen
Indicates that one entity represents a specific aspect, facet, or manifestation of a cult associated with another entity.
- 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_69c008b1c5088190ae6de2555fc05ad8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0630797f88190a5571f6000ba2e3b |
completed | March 22, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69c056037bf88190a0a3fe7429345d0b |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:23 p.m.