Triple
T28277658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Made My Excuses and Left |
E713047
|
entity |
| Predicate | hasSecondaryEmotion |
P68366
|
FINISHED |
| Object | resignation |
—
|
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: resignation | Statement: [I Made My Excuses and Left, hasSecondaryEmotion, resignation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryEmotion Context triple: [I Made My Excuses and Left, hasSecondaryEmotion, resignation]
-
A.
secondaryEmotion
chosen
Indicates that one emotion arises as a secondary, derivative, or reactive feeling in response to a primary emotion.
-
B.
secondaryMood
Indicates a secondary or accompanying emotional state that exists alongside a primary mood in a given context.
-
C.
hasSecondary
Indicates that an entity is associated with an additional or subordinate counterpart beyond its primary one.
-
D.
hasSecondarySee
Indicates that an entity has an additional, secondary “see also” reference or cross-link to another related entity.
-
E.
hasSecondarySubject
Indicates that an entity is associated with an additional, non-primary subject in a given context or relationship.
- 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_69efb52275788190ae5181ccebef18ce |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: April 27, 2026, 11:20 p.m.