Triple
T27238712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Wedding Video |
E687138
|
entity |
| Predicate | featuresProminentRole |
P39789
|
FINISHED |
| Object | Lucy Punch |
—
|
NE NERFINISHED |
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: Lucy Punch | Statement: [The Wedding Video, featuresProminentRole, Lucy Punch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresProminentRole Context triple: [The Wedding Video, featuresProminentRole, Lucy Punch]
-
A.
featuresEarlyProminentRoleFor
Indicates that something includes another entity in an early and prominently visible or important role.
-
B.
featuresStar
chosen
Indicates that one entity prominently includes or showcases another entity as a main star or featured performer.
-
C.
featuresSign
Indicates that an entity includes, displays, or incorporates a particular sign as part of its appearance, content, or design.
-
D.
featuresHero
Indicates that something (such as a work, product, or story) prominently includes or centers around a particular hero as a main character or focus.
-
E.
featuresLeader
Indicates that one entity includes, presents, or highlights another entity in the role of a leader.
- 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_69ef355547408190b5ca0d777c65040a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: April 27, 2026, 10:35 a.m.