Triple
T34562154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tams-Witmark Music Library |
E887373
|
entity |
| Predicate | notableWorkLicensed |
P146941
|
FINISHED |
| Object | Annie (musical) |
E1151959
|
NE 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: Annie (musical) | Statement: [Tams-Witmark Music Library, notableWorkLicensed, Annie (musical)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWorkLicensed Context triple: [Tams-Witmark Music Library, notableWorkLicensed, Annie (musical)]
-
A.
hasCreativeCommonsLicensedWorks
Indicates that an entity possesses or is associated with works that are licensed under a Creative Commons license.
-
B.
notableWorkUsed
Indicates that a particular notable work is utilized, referenced, or incorporated in relation to another entity or context.
-
C.
notableShowLicensed
chosen
Indicates that a show is officially licensed or authorized in a notable or significant way.
-
D.
coLicensedWith
Indicates that two or more entities share a common license or are authorized under the same licensing agreement.
-
E.
notableWork
Indicates that one entity is a significant or well-known work (such as a book, artwork, or creation) produced by another entity.
- F. None of above.
Provenance (4 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_69f349d0c4d881908dd0950f5eb9ec0a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37362840a08190a5339cef226a93c0 |
completed | June 21, 2026, 12:54 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:02 a.m.