Triple
T29212929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lal Salaam |
E740588
|
entity |
| Predicate | hasProminentCameo |
P108137
|
FINISHED |
| Object | Kapil Dev |
—
|
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: Kapil Dev | Statement: [Lal Salaam, hasProminentCameo, Kapil Dev]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProminentCameo Context triple: [Lal Salaam, hasProminentCameo, Kapil Dev]
-
A.
cameoCharacter
chosen
Indicates that one entity appears briefly or in a minor, special-guest role within the context or work associated with another entity.
-
B.
hasNotablePersonAsFace
Indicates that an entity is publicly represented or symbolized by a specific notable person, such as a spokesperson, ambassador, or brand face.
-
C.
hasProminentSupportingActor
Indicates that an entity (such as a film or show) features a supporting actor whose role or recognition is notably significant within that work.
-
D.
hasDirectorCameo
Indicates that the director of a work appears in a cameo role within that same work.
-
E.
impliedByCameo
Indicates that one fact, statement, or conclusion is inferred or supported by the appearance or brief involvement (a "cameo") of an entity in a context.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69ff519b65f081909902ba83b775ef85 |
completed | May 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69ff506fccdc8190bd93269589040aed |
completed | May 9, 2026, 3:19 p.m. |
Created at: April 28, 2026, 12:12 p.m.