Triple
T25280893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ugly Casanova |
E633821
|
entity |
| Predicate | hasOfficialRelease |
P22087
|
FINISHED |
| Object | Sharpen Your Teeth |
—
|
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: Sharpen Your Teeth | Statement: [Ugly Casanova, hasOfficialRelease, Sharpen Your Teeth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialRelease Context triple: [Ugly Casanova, hasOfficialRelease, Sharpen Your Teeth]
-
A.
hasUnofficialRelease
Indicates that an entity has a release or version that exists or is distributed outside of official or formally recognized channels.
-
B.
hasRelease
chosen
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
-
C.
hasReleased
Indicates that an entity has made another entity publicly available or officially launched it.
-
D.
isOfficialReleaseOf
Indicates that one entity is the formally authorized, final, and publicly distributed version of another entity (such as a product, work, or software).
-
E.
hasOfficial
Indicates that an entity is formally associated with, represented by, or served by a designated official or office-holder.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 1:19 p.m.