Triple
T14650656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Moon and the Yew Tree |
E343972
|
entity |
| Predicate | symbolismOfYewTree |
P107935
|
FINISHED |
| Object | death and mourning |
—
|
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: death and mourning | Statement: [The Moon and the Yew Tree, symbolismOfYewTree, death and mourning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolismOfYewTree Context triple: [The Moon and the Yew Tree, symbolismOfYewTree, death and mourning]
-
A.
treeSymbolism
Indicates the use of a tree as a symbolic representation of an idea, quality, or relationship between entities.
-
B.
oakTreeSymbolizes
Indicates that an oak tree is used as a symbol representing a particular idea, quality, or concept.
-
C.
symbolismIn
chosen
Indicates that one entity functions as a symbol or representation within the context, meaning, or interpretive framework of another entity.
-
D.
sacredTree
Indicates that an entity is regarded as a sacred or holy tree within a religious, spiritual, or cultural context.
-
E.
shapeSymbolism
Indicates how a particular shape is associated with or conveys symbolic meaning within a given context.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4ed037c8190a87bf43f839fec05 |
completed | April 14, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:26 a.m.