Triple
T7105199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Briseis |
E165563
|
entity |
| Predicate | emotionExpressed |
P23736
|
FINISHED |
| Object | grief for Patroclus |
—
|
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: grief for Patroclus | Statement: [Briseis, emotionExpressed, grief for Patroclus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emotionExpressed Context triple: [Briseis, emotionExpressed, grief for Patroclus]
-
A.
emotionEffect
Indicates that one entity’s emotional state causes or influences a change in another entity’s feelings, behavior, or condition.
-
B.
expression
Indicates that one entity is a linguistic, mathematical, or symbolic representation or manifestation of another entity.
-
C.
intendedEmotion
Indicates the emotion that an action, expression, or communication is meant to evoke in its target, regardless of the actual emotion experienced.
-
D.
faceExpression
chosen
Indicates the specific facial expression an entity is displaying, capturing its visible emotional or expressive state.
-
E.
feltIn
Indicates that a sensation, emotion, or effect is experienced within a particular location, context, or 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_69c6887fcddc8190a5d58908f6dee590 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5b892008190827fa1e5eab2e558 |
completed | March 27, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:42 p.m.