Triple
T18600501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dead family |
E454606
|
entity |
| Predicate | symbolismAssociatedWith |
P129
|
FINISHED |
| Object | burden of history |
—
|
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: burden of history | Statement: [Dead family, symbolismAssociatedWith, burden of history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolismAssociatedWith Context triple: [Dead family, symbolismAssociatedWith, burden of history]
-
A.
shapeSymbolism
Indicates how a particular shape is associated with or conveys symbolic meaning within a given context.
-
B.
symbolismFocus
Indicates that the primary emphasis of a work, element, or representation is on its symbolic meaning rather than its literal or functional aspects.
-
C.
symbolismIn
Indicates that one entity functions as a symbol or representation within the context, meaning, or interpretive framework of another entity.
-
D.
symbolizes
chosen
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
E.
emblemSymbolism
Indicates that one entity serves as an emblem whose design or features symbolically represent or convey meanings about 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5475018548190a2f497081af7ce55 |
completed | April 19, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:45 a.m.