Triple
T23491981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Fleet’s In |
E570699
|
entity |
| Predicate | songwritersInvolved |
P87641
|
FINISHED |
| Object | Jimmy Van Heusen |
—
|
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: Jimmy Van Heusen | Statement: [The Fleet’s In, songwritersInvolved, Jimmy Van Heusen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: songwritersInvolved Context triple: [The Fleet’s In, songwritersInvolved, Jimmy Van Heusen]
-
A.
songWrittenBy
Indicates that a particular song was created or composed by a specific person or group.
-
B.
songWritersInUniverse
Indicates that the specified entities are songwriters who exist or operate within a particular fictional or defined universe.
-
C.
songwritingCredit
chosen
Indicates that one entity is credited as a songwriter or co-songwriter for a musical work associated with another entity.
-
D.
hasSongwriterProducerRelationshipWith
Indicates a relationship where one entity serves as the songwriter and/or producer for another entity’s musical work.
-
E.
creditedSongwritersOfSampledWork
Indicates that the related entities are the songwriters who received official credit for the original work that was sampled in another piece of music.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7dc631c819099027e3a1c755a66 |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:05 p.m.