Triple
T34426805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Strong as Sebastian Graves |
E883696
|
entity |
| Predicate | workCriticalReception |
P2378
|
FINISHED |
| Object | mixedReviews |
—
|
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: mixedReviews | Statement: [Mark Strong as Sebastian Graves, workCriticalReception, mixedReviews]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workCriticalReception Context triple: [Mark Strong as Sebastian Graves, workCriticalReception, mixedReviews]
-
A.
criticalReception
chosen
Indicates how a work, performance, or product is evaluated and responded to by critics or professional reviewers.
-
B.
metacriticReception
Indicates the critical reception or review score an entity received on Metacritic.
-
C.
reviewCriterion
Indicates that an entity serves as a standard or basis by which another entity (such as a review or evaluation) is judged or assessed.
-
D.
hasCriticism
Indicates that one entity expresses disapproval, objection, or negative evaluation directed toward another entity.
-
E.
criticOutputs
Indicates that a critic produces or provides an evaluative response, judgment, or commentary about a target.
- 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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71947ad88819082ab9d85dd493b01 |
completed | May 3, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2 a.m.