Triple
T25358847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Invitation (2015 film) |
E635900
|
entity |
| Predicate | hasPositiveCriticalReception |
P103613
|
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 Invitation (2015 film), hasPositiveCriticalReception, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPositiveCriticalReception Context triple: [The Invitation (2015 film), hasPositiveCriticalReception, true]
-
A.
hasReceivedCriticalAcclaim
chosen
Indicates that the subject has been widely praised or positively recognized by critics or expert reviewers.
-
B.
metacriticReception
Indicates the critical reception or review score an entity received on Metacritic.
-
C.
hasNotableCritic
Indicates that one entity serves as a significant or widely recognized critic of another entity.
-
D.
criticalReception
Indicates how a work, performance, or product is evaluated and responded to by critics or professional reviewers.
-
E.
isNotedByCriticsFor
Indicates that something has been recognized and highlighted by critics specifically for a particular quality, feature, or aspect.
- 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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 21, 2026, 1:36 p.m.