Triple
T3249783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Storm |
E68147
|
entity |
| Predicate | containsSymbolism |
P129
|
FINISHED |
| Object | storm as symbol of passion |
—
|
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: storm as symbol of passion | Statement: [The Storm, containsSymbolism, storm as symbol of passion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsSymbolism Context triple: [The Storm, containsSymbolism, storm as symbol of passion]
-
A.
emblemSymbolism
Indicates that one entity serves as an emblem whose design or features symbolically represent or convey meanings about another entity.
-
B.
symbolizes
chosen
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
C.
cosmicSymbolism
Indicates a relationship where one entity symbolically represents or embodies cosmic, universal, or celestial principles in relation to another.
-
D.
clothingSymbolism
Indicates how clothing or attire conveys symbolic meaning, such as status, identity, emotion, or cultural significance, within a given context.
-
E.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
- 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_69ad858e4c708190aa31d486cfee8a6a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf3fc3c8819080ac95974581ca0e |
completed | March 8, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69ada41837e48190933572165be0ca38 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.