Triple
T2142866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toy Story 3 |
E46998
|
entity |
| Predicate | aggregatorRating |
P23408
|
FINISHED |
| Object | high rating on Rotten Tomatoes |
—
|
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: high rating on Rotten Tomatoes | Statement: [Toy Story 3, aggregatorRating, high rating on Rotten Tomatoes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aggregatorRating Context triple: [Toy Story 3, aggregatorRating, high rating on Rotten Tomatoes]
-
A.
reviewAggregator
chosen
Indicates that an entity functions as a collector and summarizer of reviews or ratings about other entities.
-
B.
ratingSystem
Indicates a system or method used to assign evaluative scores or rankings to items, actions, or entities based on defined criteria.
-
C.
rating
Indicates an evaluation relationship where one entity assigns a qualitative or quantitative score or judgment to another entity.
-
D.
hasTourismRating
Indicates that an entity has been assigned a specific tourism-related quality or rating, reflecting its appeal or suitability for tourists.
-
E.
ratingExpectation
Indicates an anticipated or predicted evaluation score that one entity expects another entity to receive or assign.
- 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_69a88a1933e0819094f18426ed74180f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbeaa14bc81908486683decd7ae42 |
completed | March 7, 2026, 5:59 a.m. |
| PD | Predicate disambiguation | batch_69abbd9846e88190b6c2941dd9ce7749 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.