Triple
T32966854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mostellaria |
E843392
|
entity |
| Predicate | audienceReactionIntended |
P63081
|
FINISHED |
| Object | laughter |
—
|
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: laughter | Statement: [Mostellaria, audienceReactionIntended, laughter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audienceReactionIntended Context triple: [Mostellaria, audienceReactionIntended, laughter]
-
A.
intendedEmotion
chosen
Indicates the emotion that an action, expression, or communication is meant to evoke in its target, regardless of the actual emotion experienced.
-
B.
audienceImpact
Indicates how an action, message, or event affects, influences, or resonates with its intended audience.
-
C.
intendedAudienceInteraction
Indicates that one entity is the target group or audience with whom another entity is meant to interact or engage.
-
D.
hasAudienceReactionType
Indicates the specific type or category of reaction an audience has in response to something (e.g., content, an event, or a performance).
-
E.
causedReaction
Indicates that one entity’s action or state brought about a specific reaction or response in another entity.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d1a306b88190a14513a21ed4f076 |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:21 a.m.