Triple
T36922164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Like Someone in Love |
E913231
|
entity |
| Predicate | hasRottenTomatoesRatingType |
P195256
|
FINISHED |
| Object | approval rating |
—
|
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: approval rating | Statement: [Like Someone in Love, hasRottenTomatoesRatingType, approval rating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRottenTomatoesRatingType Context triple: [Like Someone in Love, hasRottenTomatoesRatingType, approval rating]
-
A.
hasRottenTomatoesRating
Indicates that an entity has an associated rating value assigned by Rotten Tomatoes.
-
B.
hasRottenTomatoesEntry
Indicates that there exists a Rotten Tomatoes database entry corresponding to the given entity.
-
C.
rottenTomatoesStatus
Indicates the critical or audience evaluation status of a work as represented on Rotten Tomatoes (e.g., fresh, rotten, or certified).
-
D.
hasRatingType
chosen
Indicates that an entity is associated with a specific kind or category of rating it receives or uses.
-
E.
hasMetascore
Indicates that an entity is associated with a Metascore rating, typically representing an aggregated critical review score.
- 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: May 3, 2026, 4:13 p.m.