Triple
T7354445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The V.I.P.s |
E169586
|
entity |
| Predicate | featuresEnsembleCast |
P31694
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The V.I.P.s, featuresEnsembleCast, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresEnsembleCast Context triple: [The V.I.P.s, featuresEnsembleCast, true]
-
A.
featuresCast
Indicates that a creative work includes a particular person or group as part of its cast.
-
B.
hasEnsembleCast
chosen
Indicates that a work features an ensemble cast, meaning multiple principal performers share roughly equal prominence rather than having a single clear lead.
-
C.
partOfCastEnsembleWith
Indicates that two or more performers are members of the same cast ensemble in a shared production.
-
D.
featureCrew
Indicates that a particular crew member is highlighted or designated as a featured participant within a crew-related context.
-
E.
featuresCastType
Indicates that one entity includes or highlights a particular type or category of cast (e.g., actors or performers) associated with it.
- 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_69c68a59f2288190877ca15c19b1e822 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f139505c8190a7158cf59a6e089e |
completed | March 27, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69c6f02aeeb8819099d1626566cec18b |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:05 p.m.