Triple
T14637694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goodbye Solo |
E343647
|
entity |
| Predicate | describedByRogerEbertAs |
P976
|
FINISHED |
| Object | one of the best films of 2009 |
—
|
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: one of the best films of 2009 | Statement: [Goodbye Solo, describedByRogerEbertAs, one of the best films of 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedByRogerEbertAs Context triple: [Goodbye Solo, describedByRogerEbertAs, one of the best films of 2009]
-
A.
hasRottenTomatoesRating
Indicates that an entity has an associated rating value assigned by Rotten Tomatoes.
-
B.
describedByAuthorAs
chosen
Indicates that one entity is characterized, labeled, or portrayed in a particular way by an author.
-
C.
alsoCalledByCritics
Indicates that critics refer to the same entity by an alternative name or label.
-
D.
hasRottenTomatoesEntry
Indicates that there exists a Rotten Tomatoes database entry corresponding to the given entity.
-
E.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
- 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_69d822dffc3c8190aa173b90761bffda |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4aca6448190adf1042dfbfef716 |
completed | April 14, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69de657359c88190b082e3e9f86fc1d7 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:26 a.m.