Triple
T14601745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Royal Rascal |
E342719
|
entity |
| Predicate | shownInScene |
P73272
|
FINISHED |
| Object | opening sequence of Singin' in the Rain |
—
|
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: opening sequence of Singin' in the Rain | Statement: [The Royal Rascal, shownInScene, opening sequence of Singin' in the Rain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shownInScene Context triple: [The Royal Rascal, shownInScene, opening sequence of Singin' in the Rain]
-
A.
activeInScene
Indicates that an entity is currently present and participating within a particular scene or context.
-
B.
visibleAt
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
-
C.
positionInShow
Indicates the specific order or placement an entity occupies within a show, series, or sequence of performances or episodes.
-
D.
apparentIn
chosen
Indicates that something is visibly present, manifested, or evident within or through another thing or context.
-
E.
partOfScene
Indicates that one entity functions as a component or element within a larger scene or setting involving another entity.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb438748081908020ce04b869866a |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.