Triple
T25440509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bathouism |
E637490
|
entity |
| Predicate | holyDirection |
P124196
|
FINISHED |
| Object | east-facing altars |
—
|
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: east-facing altars | Statement: [Bathouism, holyDirection, east-facing altars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holyDirection Context triple: [Bathouism, holyDirection, east-facing altars]
-
A.
sacredDirection
chosen
Indicates a directional relationship that is regarded as holy, spiritually significant, or ritually privileged within a religious or cultural context.
-
B.
holyValley
Indicates a relationship where a valley is designated or regarded as sacred or holy, often due to religious, spiritual, or cultural significance.
-
C.
holyMountain
Indicates that a mountain is regarded as sacred or religiously significant within a particular belief system or tradition.
-
D.
holiestSiteIn
Indicates that a site is considered the most sacred or religiously significant location within a particular place or region.
-
E.
sacredTo
Indicates that one entity is regarded as holy, revered, or dedicated in honor of another entity, such as a deity, person, or concept.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6e73f308190a6e6c6e85fecaeb2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2 p.m.