Triple
T37822173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Now or Never |
E942947
|
entity |
| Predicate | featuresStuntPerformer |
P152890
|
FINISHED |
| Object | Harold Lloyd |
E34354
|
NE 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: Harold Lloyd | Statement: [Now or Never, featuresStuntPerformer, Harold Lloyd]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresStuntPerformer Context triple: [Now or Never, featuresStuntPerformer, Harold Lloyd]
-
A.
featuresStuntShow
Indicates that something includes or presents a stunt show as part of its offerings or content.
-
B.
stuntPerformerIn
Indicates that one entity serves as a stunt performer in a work, production, or performance associated with another entity.
-
C.
hasStunts
Indicates that one entity performs, includes, or is associated with stunt actions for another entity or context.
-
D.
featuresPerformerType
Indicates that something includes or highlights a performer of a specified type (e.g., musician, actor, or other performance role).
-
E.
featuresOnScreenPerformer
chosen
Indicates that something (such as a work or production) includes a particular performer visibly appearing on screen.
- F. None of above.
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_69f76ee987588190906506e759be5db3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41041470c4819092a7d29c3a85f333 |
completed | June 28, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.