Triple
T23687268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ἀνδρόγεως |
E585202
|
entity |
| Predicate | hasCultOrHeroon |
P63978
|
FINISHED |
| Object | Attica |
—
|
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: Attica | Statement: [Ἀνδρόγεως, hasCultOrHeroon, Attica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCultOrHeroon Context triple: [Ἀνδρόγεως, hasCultOrHeroon, Attica]
-
A.
hasCultFeature
Indicates that an entity possesses a characteristic, attribute, or element associated with cultic or ritual practices.
-
B.
hasCultLeaderCharacter
Indicates that an entity includes or features a character who acts as a cult leader, exerting charismatic, manipulative, and controlling influence over a group.
-
C.
hasCultSince
Indicates that an entity has had an organized group of devoted followers (a cult) continuously since a specified time or date.
-
D.
hasCultPredecessor
Indicates that one cult, tradition, or religious practice is considered to be derived from, influenced by, or historically preceded by another cult.
-
E.
hasNotableHero
chosen
Indicates that an entity is associated with a particularly distinguished or prominent hero.
- 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_69e249037ce0819088b149608e98f685 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b5bf1c10819085d48c4225cc63fc |
completed | April 29, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:52 p.m.