Triple
T15019998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anomalisa |
E378057
|
entity |
| Predicate | filmRatingRottenTomatoes |
P36846
|
FINISHED |
| Object | high critical approval |
—
|
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: high critical approval | Statement: [Anomalisa, filmRatingRottenTomatoes, high critical approval]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filmRatingRottenTomatoes Context triple: [Anomalisa, filmRatingRottenTomatoes, high critical approval]
-
A.
hasRottenTomatoesRating
Indicates that an entity has an associated rating value assigned by Rotten Tomatoes.
-
B.
rottenTomatoesStatus
chosen
Indicates the critical or audience evaluation status of a work as represented on Rotten Tomatoes (e.g., fresh, rotten, or certified).
-
C.
hasRottenTomatoesEntry
Indicates that there exists a Rotten Tomatoes database entry corresponding to the given entity.
-
D.
USRating
Indicates that an entity has been assigned a rating, classification, or evaluation according to a United States–based standard or system.
-
E.
mpaaRating
Indicates the official Motion Picture Association of America (MPAA) content rating assigned to a film or audiovisual work.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded76445988190984b57de66e00c4a |
completed | April 15, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69de9a67cbc481909c19c2de57de4eb7 |
completed | April 14, 2026, 7:50 p.m. |
Created at: April 10, 2026, 2:56 a.m.