Triple
T12886507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nobody’s Business |
E308236
|
entity |
| Predicate | hasCollectionCriticalReception |
P103613
|
FINISHED |
| Object | widely acclaimed by literary critics |
—
|
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: widely acclaimed by literary critics | Statement: [Nobody’s Business, hasCollectionCriticalReception, widely acclaimed by literary critics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollectionCriticalReception Context triple: [Nobody’s Business, hasCollectionCriticalReception, widely acclaimed by literary critics]
-
A.
hasCriticism
Indicates that one entity expresses disapproval, objection, or negative evaluation directed toward another entity.
-
B.
hasNotableCritic
Indicates that one entity serves as a significant or widely recognized critic of another entity.
-
C.
hasReceivedCriticalAcclaim
chosen
Indicates that the subject has been widely praised or positively recognized by critics or expert reviewers.
-
D.
criticalReception
Indicates how a work, performance, or product is evaluated and responded to by critics or professional reviewers.
-
E.
metacriticReception
Indicates the critical reception or review score an entity received on Metacritic.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97c7f91d08190aac2f6419d3ba992 |
completed | April 10, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69d96fa55b888190ab1612e93c41aec4 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:39 p.m.