Triple
T33715891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taylor Parks |
E863871
|
entity |
| Predicate | hasNotableSongwritingCreditFor |
P47055
|
FINISHED |
| Object | Love Lies |
E245939
|
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: Love Lies | Statement: [Taylor Parks, hasNotableSongwritingCreditFor, Love Lies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSongwritingCreditFor Context triple: [Taylor Parks, hasNotableSongwritingCreditFor, Love Lies]
-
A.
hasWrittenLyricsFor
Indicates that one entity is the lyricist who has created the words for a song or musical work performed or associated with another entity.
-
B.
hasWrittenSongsFor
Indicates that one entity has composed songs specifically intended to be performed, recorded, or used by another entity.
-
C.
hasSongwriterProducerRelationshipWith
Indicates a relationship where one entity serves as the songwriter and/or producer for another entity’s musical work.
-
D.
hasWritingCreditOn
chosen
Indicates that an entity is credited as a writer or co-writer for a particular work or production.
-
E.
hasPrimarySongwriter
Indicates that one entity serves as the main or principal songwriter responsible for creating the songs associated with 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01e27bb77c8190a7686b77a524f177 |
completed | May 11, 2026, 2:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a367600372081908feefb8955dc0418 |
completed | June 20, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_6a01da2614788190b31db15539f5ba58 |
completed | May 11, 2026, 1:31 p.m. |
Created at: May 1, 2026, 1:44 a.m.