Triple
T26988960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beta |
E679808
|
entity |
| Predicate | maskSymbolism |
P107935
|
FINISHED |
| Object | rejection of former identity |
—
|
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: rejection of former identity | Statement: [Beta, maskSymbolism, rejection of former identity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maskSymbolism Context triple: [Beta, maskSymbolism, rejection of former identity]
-
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
chosen
Indicates that one entity functions as a symbol or representation within the context, meaning, or interpretive framework of another entity.
-
D.
languageOfSymbolism
Indicates that one entity is the language in which the symbolic meaning or symbolism of another entity is expressed or encoded.
-
E.
fieldSymbolism
Indicates the symbolic meaning or thematic associations that a field (as a setting, area, or domain) conveys 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6218de4ec81908d3001e5b8748c7d |
completed | May 2, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:50 a.m.