Triple
T20224032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mia (Love Actually) |
E495328
|
entity |
| Predicate | setsUpConflictFor |
P75326
|
FINISHED |
| Object | Harry and Karen’s relationship arc |
—
|
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: Harry and Karen’s relationship arc | Statement: [Mia (Love Actually), setsUpConflictFor, Harry and Karen’s relationship arc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsUpConflictFor Context triple: [Mia (Love Actually), setsUpConflictFor, Harry and Karen’s relationship arc]
-
A.
conflictWith
Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
-
B.
triggersConflict
chosen
Indicates that one entity initiates or causes a dispute, clash, or incompatibility to arise with another entity or within a system.
-
C.
settingConflict
Indicates a conflict or incompatibility between two settings, configurations, or environmental conditions.
-
D.
namedForConflict
Indicates that one entity is named after, or in commemoration of, a specific conflict, war, or battle.
-
E.
appliesToConflictWith
Indicates that one element’s scope, rules, or effects are relevant to a conflict involving another element, defining how that element is implicated in or governed by the conflict.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd827708190b798a30f4e7d533f |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.