Triple
T23695509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Savior of the World |
E585433
|
entity |
| Predicate | showsGesture |
P16866
|
FINISHED |
| Object | Christ giving blessing |
—
|
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: Christ giving blessing | Statement: [Savior of the World, showsGesture, Christ giving blessing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showsGesture Context triple: [Savior of the World, showsGesture, Christ giving blessing]
-
A.
usesHandGestures
Indicates that an entity communicates or expresses itself by making deliberate movements or signals with its hands.
-
B.
signatureGesture
Indicates a distinctive or characteristic gesture that is uniquely associated with a particular individual or entity.
-
C.
openingGesture
Indicates an initial movement or action that begins or invites the start of an interaction, event, or sequence.
-
D.
gesture
chosen
Indicates that an entity uses a bodily movement or sign to communicate or express something to another entity.
-
E.
showsThat
Indicates that one entity demonstrates, proves, or provides evidence for the truth or validity of another.
- 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_69e24904bd508190abfcb74855de2918 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b5c53cb88190a1964999f8ccb4cf |
completed | April 29, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:52 p.m.