Triple
T1084360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chrismation in Eastern Christianity |
E24016
|
entity |
| Predicate | hasPrimarySymbol |
P10282
|
FINISHED |
| Object | holy chrism |
—
|
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: holy chrism | Statement: [Chrismation in Eastern Christianity, hasPrimarySymbol, holy chrism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimarySymbol Context triple: [Chrismation in Eastern Christianity, hasPrimarySymbol, holy chrism]
-
A.
hasPrimaryFunction
Indicates that one entity serves as the main or principal function or role of another entity.
-
B.
hasPrimarySee
Indicates that one entity is designated as the main or preferred "see" reference or cross-reference for another entity.
-
C.
hasColorSymbol
Indicates that one entity is associated with another entity that serves as its representative or symbolic color.
-
D.
hasSymbolNamedAfter
Indicates that one entity has a symbol whose name is derived from or dedicated to another entity.
-
E.
hasTraditionalSymbol
chosen
Indicates that something is associated with or represented by a conventional or culturally established symbol.
- 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.