Triple
T30734101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jurassic Park III (film score) |
E782498
|
entity |
| Predicate | originalThemesBy |
P141573
|
FINISHED |
| Object | Don Davis |
—
|
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: Don Davis | Statement: [Jurassic Park III (film score), originalThemesBy, Don Davis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalThemesBy Context triple: [Jurassic Park III (film score), originalThemesBy, Don Davis]
-
A.
featuresThemeBy
Indicates that something (such as a work, event, or product) prominently includes or centers around a particular theme created or defined by a specified source or entity.
-
B.
usesThemeBy
chosen
Indicates that one entity incorporates, applies, or is based on a theme that was created, defined, or provided by another entity.
-
C.
themeExamples
Indicates that the related entity serves as an example or illustration of the theme expressed by the subject.
-
D.
usesThemeFrom
Indicates that one work incorporates, references, or is based on the thematic material of another work.
-
E.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0067cde0f08190b2cd93af5f00d519 |
completed | May 10, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_6a0065820c8c8190994734433c64a30a |
completed | May 10, 2026, 11:01 a.m. |
Created at: April 29, 2026, 8:37 p.m.