Triple
T24807671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cappadocians |
E620696
|
entity |
| Predicate | religiousInfluences |
P29112
|
FINISHED |
| Object | Greek polytheism |
—
|
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: Greek polytheism | Statement: [Cappadocians, religiousInfluences, Greek polytheism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousInfluences Context triple: [Cappadocians, religiousInfluences, Greek polytheism]
-
A.
influencedReligion
Indicates that one entity has had a shaping or modifying effect on the religious beliefs, practices, or traditions of another entity.
-
B.
influencedByReligion
chosen
Indicates that an entity’s characteristics, decisions, or development are shaped or affected by religious beliefs, practices, or institutions.
-
C.
religiousSpectrum
Indicates a relationship that places entities along a range or continuum of religious belief, practice, or affiliation.
-
D.
religionOrBelief
Indicates that one entity holds, practices, or is associated with a particular religion, faith, or belief system.
-
E.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 4:50 a.m.