Triple
T28896535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appaloosa Interactive |
E732847
|
entity |
| Predicate | hasWorkWithSharkTheme |
P146957
|
FINISHED |
| Object | Jaws Unleashed |
—
|
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: Jaws Unleashed | Statement: [Appaloosa Interactive, hasWorkWithSharkTheme, Jaws Unleashed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkWithSharkTheme Context triple: [Appaloosa Interactive, hasWorkWithSharkTheme, Jaws Unleashed]
-
A.
hasSharkAntagonist
chosen
Indicates that an entity features a shark serving as an opposing or hostile force, often in a central conflict role.
-
B.
hasWorkWithDinosaurTheme
Indicates that an entity is associated with a work whose subject matter or theme prominently involves dinosaurs.
-
C.
SharksTries
Indicates an attempt or effort made by sharks to perform an action or achieve a particular outcome.
-
D.
hasMotiveTheme
Indicates that an action, event, or situation is associated with a central motivating theme or underlying driving idea.
-
E.
hasSuperpowersTheme
Indicates that the subject involves, features, or centers around the theme of characters possessing superhuman abilities or powers.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 28, 2026, 7:59 a.m.