Triple
T4443564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Limbo |
E96226
|
entity |
| Predicate | metacriticStatus |
P40660
|
FINISHED |
| Object | critically acclaimed |
—
|
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: critically acclaimed | Statement: [Limbo, metacriticStatus, critically acclaimed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metacriticStatus Context triple: [Limbo, metacriticStatus, critically acclaimed]
-
A.
metacriticCategory
Indicates that one entity is classified under a specific Metacritic-defined category (such as a media type, genre, or section) in the Metacritic system.
-
B.
hasMetascore
chosen
Indicates that an entity is associated with a Metascore rating, typically representing an aggregated critical review score.
-
C.
rottenTomatoesStatus
Indicates the critical or audience evaluation status of a work as represented on Rotten Tomatoes (e.g., fresh, rotten, or certified).
-
D.
hasMetacriticId
Indicates that an entity is associated with a specific identifier used by Metacritic to reference it in their database.
-
E.
hasRottenTomatoesRating
Indicates that an entity has an associated rating value assigned by Rotten Tomatoes.
- 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355b052688190a0d8e5912f82151c |
completed | March 13, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69b34f62c180819097ced38da2052207 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:32 p.m.