Triple
T36671961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R. K. Films |
E905440
|
entity |
| Predicate | creativeControlOftenHeldBy |
P64133
|
FINISHED |
| Object | Raj Kapoor |
—
|
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: Raj Kapoor | Statement: [R. K. Films, creativeControlOftenHeldBy, Raj Kapoor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creativeControlOftenHeldBy Context triple: [R. K. Films, creativeControlOftenHeldBy, Raj Kapoor]
-
A.
creativeControlHeldBy
chosen
Indicates that authority over creative decisions or direction is held by a particular entity.
-
B.
endedControlOf
Indicates that one entity has ceased to exercise authority, influence, or governance over another entity or domain.
-
C.
usedToControl
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
-
D.
controlsWith
Indicates that one entity exercises authority, direction, or regulatory power over another entity through specific means or mechanisms.
-
E.
effectControlledBy
Indicates that the occurrence, magnitude, or outcome of one effect is regulated, determined, or constrained by another specified factor or agent.
- 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_69f76e6f10008190aea41746aa1b186e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffb1218cb08190a814c7f0833501a7 |
completed | May 9, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69ffb083d6988190b2757e0cfd629b75 |
completed | May 9, 2026, 10:09 p.m. |
Created at: May 3, 2026, 4:12 p.m.