Triple
T5617605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orthia |
E147516
|
entity |
| Predicate | locatedInReligion |
P31425
|
FINISHED |
| Object | ancient 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: ancient Greek polytheism | Statement: [Orthia, locatedInReligion, ancient Greek polytheism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInReligion Context triple: [Orthia, locatedInReligion, ancient Greek polytheism]
-
A.
positionInReligion
Indicates the specific role, rank, or office an entity holds within a religious organization or tradition.
-
B.
appearsInReligion
chosen
Indicates that one entity is featured, referenced, or plays a role within the religious context, texts, or traditions associated with another entity.
-
C.
isPlaceOfWorshipFor
Indicates that a location serves as a site where members of a particular religion or belief system perform worship or religious practices.
-
D.
isUsedByReligion
Indicates that something (such as an object, practice, text, or symbol) is employed or utilized within the context of a particular religion.
-
E.
positionOnStateReligion
Indicates a stance or viewpoint regarding the role, status, or legitimacy of an official state 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_69c00905d4588190bd967842bbcf2219 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c021dc04c081909f36e40394e7c955 |
completed | March 22, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.