Triple
T33599372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark (Love Actually) |
E860672
|
entity |
| Predicate | hidesFeelingsBy |
P171507
|
FINISHED |
| Object | acting distant toward Juliet |
—
|
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: acting distant toward Juliet | Statement: [Mark (Love Actually), hidesFeelingsBy, acting distant toward Juliet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hidesFeelingsBy Context triple: [Mark (Love Actually), hidesFeelingsBy, acting distant toward Juliet]
-
A.
hidesFeelings
chosen
Indicates that one entity deliberately conceals or suppresses their emotions or emotional state from others.
-
B.
feels
Indicates that an entity experiences or has a particular emotion, sensation, or internal state in relation to something.
-
C.
feltIn
Indicates that a sensation, emotion, or effect is experienced within a particular location, context, or entity.
-
D.
hiddenIn
Indicates that one entity is concealed within, behind, or inside another entity so that it is not readily visible or apparent.
-
E.
hidesFrom
Indicates that one entity actively avoids being seen, detected, or encountered by 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_69f3497f35908190a2e9bbb9b96c7a3f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:41 a.m.