Triple
T22428024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emmett |
E554422
|
entity |
| Predicate | targetAudienceRatingOfWork |
P59739
|
FINISHED |
| Object | PG-13 (A Quiet Place Part II) |
—
|
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: PG-13 (A Quiet Place Part II) | Statement: [Emmett, targetAudienceRatingOfWork, PG-13 (A Quiet Place Part II)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetAudienceRatingOfWork Context triple: [Emmett, targetAudienceRatingOfWork, PG-13 (A Quiet Place Part II)]
-
A.
targetAudienceRatingContext
Indicates the contextual conditions or setting (such as platform, region, or usage scenario) under which a particular audience rating is intended to apply.
-
B.
targetAudienceRank
Indicates the relative priority or importance level assigned to a particular audience segment compared to other potential audiences.
-
C.
targetAudienceOfOriginWork
Indicates the intended audience or demographic group for which the original work was created.
-
D.
ratingOfWork
Indicates the evaluative score or assessment assigned to a particular work or creation.
-
E.
hasRatingLevel
chosen
Indicates that an entity is associated with a particular rating level or score category.
- 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_69e11e4f2d0c819091aa3558ea2ee630 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15a2f054c819093fbe173c8a4a544 |
completed | April 29, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.