Triple
T32924745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayyám-i-Há |
E842235
|
entity |
| Predicate | symbolismOfLetterHá |
P107935
|
FINISHED |
| Object | Essence of God |
—
|
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: Essence of God | Statement: [Ayyám-i-Há, symbolismOfLetterHá, Essence of God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolismOfLetterHá Context triple: [Ayyám-i-Há, symbolismOfLetterHá, Essence of God]
-
A.
symbolismOfName
Indicates that a name functions as a symbol, representing deeper meanings, qualities, or concepts beyond its literal reference.
-
B.
emblemSymbolism
Indicates that one entity serves as an emblem whose design or features symbolically represent or convey meanings about another entity.
-
C.
languageOfSymbolism
Indicates that one entity is the language in which the symbolic meaning or symbolism of another entity is expressed or encoded.
-
D.
symbolismIn
chosen
Indicates that one entity functions as a symbol or representation within the context, meaning, or interpretive framework of another entity.
-
E.
symbolismFocus
Indicates that the primary emphasis of a work, element, or representation is on its symbolic meaning rather than its literal or functional aspects.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:20 a.m.