Triple
T14898937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penrod’s Double Trouble (1938 film) |
E359949
|
entity |
| Predicate | featuresActorType |
P56852
|
FINISHED |
| Object | child actor |
—
|
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: child actor | Statement: [Penrod’s Double Trouble (1938 film), featuresActorType, child actor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresActorType Context triple: [Penrod’s Double Trouble (1938 film), featuresActorType, child actor]
-
A.
featuresCastType
chosen
Indicates that one entity includes or highlights a particular type or category of cast (e.g., actors or performers) associated with it.
-
B.
actingRoleType
Indicates the specific type or category of role an entity performs when acting in a particular capacity or function.
-
C.
featuresActorInMultipleRoles
Indicates that a work includes an actor who portrays more than one distinct role within that same work.
-
D.
featuresPerformerType
Indicates that something includes or highlights a performer of a specified type (e.g., musician, actor, or other performance role).
-
E.
featuresCast
Indicates that a creative work includes a particular person or group as part of its cast.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded6084574819098033a9723f3e1c4 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a4a14a88190951bb8f4c60bd37b |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:11 a.m.