Triple
T10368034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luke (Love Actually) |
E244305
|
entity |
| Predicate | hasScreenAppearanceType |
P93610
|
FINISHED |
| Object | supporting character |
—
|
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: supporting character | Statement: [Luke (Love Actually), hasScreenAppearanceType, supporting character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScreenAppearanceType Context triple: [Luke (Love Actually), hasScreenAppearanceType, supporting character]
-
A.
hasScreen
Indicates that an entity is equipped with or includes a screen or display component.
-
B.
hasDisplayType
Indicates the type or category of display associated with an entity, such as the format, mode, or presentation style used to show its content.
-
C.
hasMediaAppearanceIn
Indicates that an entity appears or is featured as media content within a specified media work, program, or publication.
-
D.
hasTopScreenSize
Indicates that an entity (typically a device) possesses a top screen with a specified size or dimension.
-
E.
hasColorType
Indicates that an entity is associated with a specific category or type of color.
- F. None of above. chosen
Provenance (4 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e97106448190a075948e63184f47 |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dface5508190a7b42f01ad0a19a2 |
completed | April 7, 2026, 10:42 a.m. |
| PDg | Predicate description generation | batch_69d4e944fac4819093b0312aa0efd729 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:01 p.m.