Triple
T8626126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goodbye to Language |
E204283
|
entity |
| Predicate | hasMetacriticCategory |
P54693
|
FINISHED |
| Object | film |
—
|
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: film | Statement: [Goodbye to Language, hasMetacriticCategory, film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMetacriticCategory Context triple: [Goodbye to Language, hasMetacriticCategory, film]
-
A.
hasMetacriticId
Indicates that an entity is associated with a specific identifier used by Metacritic to reference it in their database.
-
B.
metacriticCategory
chosen
Indicates that one entity is classified under a specific Metacritic-defined category (such as a media type, genre, or section) in the Metacritic system.
-
C.
hasMetacriticPage
Indicates that an entity has a dedicated page or entry on the Metacritic review aggregation website.
-
D.
hasMetascore
Indicates that an entity is associated with a Metascore rating, typically representing an aggregated critical review score.
-
E.
MetascoreBasedOn
Indicates that a metascore is calculated or derived based on a specified set of reviews, ratings, or sources.
- 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_69ca834a4ea0819094970dceb9e389f3 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5730309081909a9a0256c9bf5f8f |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc455906f8819082edd79cb4a1cf28 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:26 p.m.