Triple
T34936757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Last Rodeo |
E1007595
|
entity |
| Predicate | sharesGenreWithOtherWorksByAuthor |
P98868
|
FINISHED |
| Object | The Big Sky |
—
|
NE NERFINISHED |
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: The Big Sky | Statement: [The Last Rodeo, sharesGenreWithOtherWorksByAuthor, The Big Sky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesGenreWithOtherWorksByAuthor Context triple: [The Last Rodeo, sharesGenreWithOtherWorksByAuthor, The Big Sky]
-
A.
authorOfSameGenre
Indicates that two authors primarily write works within the same literary genre.
-
B.
hasAuthorOfSameWorkAs
Indicates that two authors are related by having written or contributed to the same work.
-
C.
hasWorkInGenreOfAuthor
Indicates that a work is associated with an author whose typical or primary genre matches the genre of that work.
-
D.
workByAuthorAlsoKnownFor
Indicates that a work is created by an author who is also notably recognized for another specified work or contribution.
-
E.
workBySameAuthorAs
chosen
Indicates that two works share the same author, i.e., they were created by the same person or entity.
- 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_69f76dc513fc819084a1ff52abbfa5bc |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0049e40d60819081e3899d8d9fca51 |
completed | May 10, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_6a0048c47b548190ad31b2901cc3784a |
completed | May 10, 2026, 8:58 a.m. |
Created at: May 3, 2026, 4 p.m.