Triple
T17912619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinestro |
E447849
|
entity |
| Predicate | emotionalSpectrumAssociation |
P111838
|
FINISHED |
| Object | fear |
—
|
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: fear | Statement: [Sinestro, emotionalSpectrumAssociation, fear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emotionalSpectrumAssociation Context triple: [Sinestro, emotionalSpectrumAssociation, fear]
-
A.
emotionSpectrumAffiliation
chosen
Indicates an entity’s association or alignment with a particular range or category of emotions along an emotional spectrum.
-
B.
emotionAssociation
Indicates an emotional relationship or connection that one entity has toward another entity or concept.
-
C.
emotionalTrait
Indicates that an entity possesses a particular emotional characteristic, disposition, or affective quality.
-
D.
emotionalCounterpartOf
Indicates that one entity serves as the emotional equivalent, complement, or matching emotional role of another entity.
-
E.
emotionDomain
Indicates the general emotional category or type to which a specific emotion belongs (e.g., grouping emotions into broader domains like joy, anger, or fear).
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a30288ac8190bc633e69447709bf |
completed | April 19, 2026, 9:40 a.m. |
| PD | Predicate disambiguation | batch_69e3d8ec2f6881909d7f54b878cbed37 |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:19 a.m.