Triple
T35892137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Impractical Jokers: The Movie |
E1038111
|
entity |
| Predicate | featuresRealPeople |
P193877
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Impractical Jokers: The Movie, featuresRealPeople, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresRealPeople Context triple: [Impractical Jokers: The Movie, featuresRealPeople, yes]
-
A.
featuresPeople
chosen
Indicates that something prominently includes or showcases specific people as part of its content or presentation.
-
B.
featuresResponseOfPeople
Indicates a relationship where something presents or includes the reactions, opinions, or feedback expressed by people.
-
C.
featuresRealPersonAsHimself
Indicates that a real person appears in the work portraying themself rather than a fictional character.
-
D.
metPerson
Indicates that one person has encountered or come into contact with another person, typically in a face-to-face meeting.
-
E.
featuresRealLife
Indicates that something includes or portrays real-life people, events, situations, or elements rather than fictional or purely abstract ones.
- 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_69f76e2190f88190beb2eed798a4ef01 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.