Triple
T20211710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mia (Love Actually) |
E493500
|
entity |
| Predicate | notableGiftInPlot |
P112925
|
FINISHED |
| Object | gold necklace from Harry |
—
|
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: gold necklace from Harry | Statement: [Mia (Love Actually), notableGiftInPlot, gold necklace from Harry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGiftInPlot Context triple: [Mia (Love Actually), notableGiftInPlot, gold necklace from Harry]
-
A.
notableWorkInPlot
Indicates that a work is prominently featured or plays a significant role within the plot of another work.
-
B.
notableBequest
Indicates that one entity is a significant or historically notable bequest, legacy, or inheritance made by another entity.
-
C.
notableFeatureInStory
chosen
Indicates that a particular feature, element, or characteristic plays a significant or prominent role within a story.
-
D.
giftBrought
Indicates that one entity brought or presented a gift to another entity.
-
E.
notableRelic
Indicates that an entity is a historically or culturally significant relic associated with another entity (such as a place, person, 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ed627f48190a8ba638b85977af3 |
completed | April 20, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:38 p.m.