Triple
T1084383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chrismation in Eastern Christianity |
E24016
|
entity |
| Predicate | liturgicalLocationOnBody |
P21283
|
FINISHED |
| Object | forehead |
—
|
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: forehead | Statement: [Chrismation in Eastern Christianity, liturgicalLocationOnBody, forehead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalLocationOnBody Context triple: [Chrismation in Eastern Christianity, liturgicalLocationOnBody, forehead]
-
A.
seatOfBody
Indicates that one entity serves as the physical location or base where another entity (typically an organization or authority) is situated or headquartered.
-
B.
hasBodyRegion
chosen
Indicates that an entity possesses, includes, or is associated with a specific anatomical or bodily region.
-
C.
liturgicalSetting
Indicates the specific religious or worship context in which a liturgical text, action, or element is intended to be used.
-
D.
seatOnBody
Indicates that one entity functions as a seat or seating surface that is physically attached or integrated to a body or body-like structure.
-
E.
positionInChurch
Indicates that one entity holds a specific role, office, or rank within a church organization or hierarchy.
- 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9608bac819085196cc0f8fbb2e7 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b7407914819092ed933a7316b450 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.