Triple
T29055377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urartian religion |
E735370
|
entity |
| Predicate | sacredSymbol_Shivini |
P5607
|
FINISHED |
| Object | solar disk |
—
|
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: solar disk | Statement: [Urartian religion, sacredSymbol_Shivini, solar disk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sacredSymbol_Shivini Context triple: [Urartian religion, sacredSymbol_Shivini, solar disk]
-
A.
sacredElement
Indicates that one entity is regarded as holy, revered, or spiritually significant within the religious or cultural context of the other entity.
-
B.
sacredTo
Indicates that one entity is regarded as holy, revered, or dedicated in honor of another entity, such as a deity, person, or concept.
-
C.
sacredColor
Indicates that a particular color is regarded as holy, revered, or religiously significant in relation to an entity or context.
-
D.
hasSacredSymbol
chosen
Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
-
E.
sacredHill
Indicates that a hill holds religious or spiritual significance within a belief system or tradition.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66091e30081908396b27a885d36b1 |
completed | May 2, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 10:11 a.m.