Triple
T21109592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raja Harishchandra (1913 film) |
E520137
|
entity |
| Predicate | hasSurvivingFootage |
P2248
|
FINISHED |
| Object | partial |
—
|
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: partial | Statement: [Raja Harishchandra (1913 film), hasSurvivingFootage, partial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurvivingFootage Context triple: [Raja Harishchandra (1913 film), hasSurvivingFootage, partial]
-
A.
hasLiveActionFilm
Indicates that a subject has a corresponding live-action film adaptation or representation.
-
B.
survivesEventsOfFilm
Indicates that an entity remains alive or intact through all the events depicted in a film.
-
C.
hasSurvivingOriginals
chosen
Indicates that some of the original instances or versions of an entity still exist and have not been lost, destroyed, or replaced.
-
D.
hasSurvivors
Indicates that one or more entities continue to exist or remain alive after a particular event, condition, or incident.
-
E.
hasBehindTheScenesFilm
Indicates that one work includes or is associated with a behind-the-scenes film documenting its creation or production process.
- 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_69e0b509a318819092fbbcb21d1fe603 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7210110a48190a6359b6732f6293d |
completed | April 21, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_69e5dbff56848190a03b350a9305c612 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:54 p.m.