Triple
T33694504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabians |
E863265
|
entity |
| Predicate | worshipDirection |
P13035
|
FINISHED |
| Object | celestial bodies |
—
|
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: celestial bodies | Statement: [Sabians, worshipDirection, celestial bodies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshipDirection Context triple: [Sabians, worshipDirection, celestial bodies]
-
A.
liturgicalOrientation
chosen
Indicates the directional or positional alignment used in a religious or liturgical context, such as the way worship or ritual is oriented in space.
-
B.
sacredDirection
Indicates a directional relationship that is regarded as holy, spiritually significant, or ritually privileged within a religious or cultural context.
-
C.
worshipArea
Indicates a spatial or locational relationship where an area is designated or used for worship or religious practices.
-
D.
mainShrineOrientation
Indicates the directional alignment or facing direction of a main shrine relative to a reference point or axis.
-
E.
worshipType
Indicates the manner or form in which worship is practiced or expressed in a religious or spiritual context.
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fa8838c48190b2865234f4aa9c2d |
completed | May 3, 2026, 7:34 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:43 a.m.