Triple
T14611575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Still in Love |
E342972
|
entity |
| Predicate | hasMusicalArtistOccupation |
P115040
|
FINISHED |
| Object | American singer-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: American singer-songwriter | Statement: [Still in Love, hasMusicalArtistOccupation, American singer-songwriter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicalArtistOccupation Context triple: [Still in Love, hasMusicalArtistOccupation, American singer-songwriter]
-
A.
hasMusicalArtistType
Indicates that an entity has a specific role or classification as a type of musical artist (e.g., solo artist, band, composer).
-
B.
hasMainPerformerOccupation
Indicates that an entity’s primary or main performer is associated with a specified occupation or professional role.
-
C.
hasArtistRole
Indicates that an entity serves in the capacity or role of an artist in relation to another entity or context.
-
D.
hasMusicalWorkType
Indicates that a musical work is associated with a specific type or category of musical composition.
-
E.
hasArtist
Indicates that an entity (such as a work or item) is associated with or created by a specific artist.
- F. None of above. chosen
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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb450e6588190a94488d8e71888c8 |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:25 a.m.