Triple
T23388586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ostensorium |
E593949
|
entity |
| Predicate | oftenCoveredWith |
P64883
|
FINISHED |
| Object | humeral veil during 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: humeral veil during blessing | Statement: [ostensorium, oftenCoveredWith, humeral veil during blessing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenCoveredWith Context triple: [ostensorium, oftenCoveredWith, humeral veil during blessing]
-
A.
typicallyCovers
Indicates that one entity is the kind of thing that usually or normally includes, addresses, or encompasses another entity.
-
B.
hasCoverings
chosen
Indicates that one entity possesses or is equipped with protective or enclosing layers, surfaces, or coverings provided by another entity.
-
C.
bodyCoverage
Indicates the extent or proportion of an entity’s body that is covered by another substance, material, or feature.
-
D.
isCoveredIn
Indicates that one entity has its surface or area overlaid, coated, or blanketed by another substance or material.
-
E.
bodyCovering
Indicates the type of external covering or surface (such as skin, fur, feathers, or scales) that characterizes an entity’s body.
- 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a499bad88190afca1afb2e3fddb0 |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:35 p.m.