Triple
T36869119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Orthodox Old-Rite Church |
E911176
|
entity |
| Predicate | usesSignOfCross |
P195376
|
FINISHED |
| Object | two-finger sign of the cross |
—
|
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: two-finger sign of the cross | Statement: [Russian Orthodox Old-Rite Church, usesSignOfCross, two-finger sign of the cross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSignOfCross Context triple: [Russian Orthodox Old-Rite Church, usesSignOfCross, two-finger sign of the cross]
-
A.
crossOf
Indicates that one entity is the cross or hybrid resulting from the combination or breeding of two other entities.
-
B.
tookTheCross
Indicates that a person formally committed to participate in a crusade or holy war, typically by taking a religious vow or symbol.
-
C.
numberOfNotchesOnCrosier
Indicates the relationship that specifies how many notches are present on a given crosier.
-
D.
traditionalSideOfCross
Indicates the side of a cross that is considered the customary or historically recognized orientation in a given tradition.
-
E.
materialOfCrosses
Indicates that one entity is the material from which another entity’s crosses are made.
- F. None of above. chosen
Provenance (4 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_69f76e80f6f0819091cba8e19b269615 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69fdbc5da9988190b95234bce4cc2062 |
completed | May 8, 2026, 10:35 a.m. |
Created at: May 3, 2026, 4:13 p.m.