Triple
T26951515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | punctum |
E678786
|
entity |
| Predicate | effectOnViewer |
P53532
|
FINISHED |
| Object | emotional shock |
—
|
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: emotional shock | Statement: [punctum, effectOnViewer, emotional shock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnViewer Context triple: [punctum, effectOnViewer, emotional shock]
-
A.
effectOnViewers
chosen
Indicates the impact or influence that something has on those who observe or experience it.
-
B.
effectOnUser
Indicates how an action, event, or condition influences or impacts a user.
-
C.
effectOnRepresentation
Indicates how one entity influences, alters, or determines the form, quality, or characteristics of another entity’s representation.
-
D.
effectOnOthers
Indicates the impact or influence that one entity’s actions, presence, or state has on other entities.
-
E.
eventEffect
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
- 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_69eeeb4e75f08190b14fc91ca4a91488 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 6:24 a.m.