Triple
T16761878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | You Are My Destiny |
E407364
|
entity |
| Predicate | hasWriterRole |
P97835
|
FINISHED |
| Object | Paul Anka as songwriter |
—
|
LITERAL 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: Paul Anka as songwriter | Statement: [You Are My Destiny, hasWriterRole, Paul Anka as songwriter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWriterRole Context triple: [You Are My Destiny, hasWriterRole, Paul Anka as songwriter]
-
A.
hasAuthorRoleFor
chosen
Indicates that an entity serves in the role of author for another entity, such as a work, document, or publication.
-
B.
hasCreatorRoleFor
Indicates that an entity serves in the role of creator for another entity, establishing a creator-to-created relationship.
-
C.
hasWriterBlock
Indicates that an entity (typically a writer) is experiencing difficulty producing written work due to a creative or mental block.
-
D.
activeAsWriterFrom
Indicates the time period from which an entity began being active in the role of a writer.
-
E.
hasAuthor
Indicates that an entity is written or created by a specific author.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3abed67f88190afb1d392ff01a5e7 |
completed | April 18, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.