Triple
T38182638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Invictus Records |
E1005212
|
entity |
| Predicate | notableSongwriterTeam |
P20008
|
FINISHED |
| Object | Holland–Dozier–Holland |
E295707
|
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: Holland–Dozier–Holland | Statement: [Invictus Records, notableSongwriterTeam, Holland–Dozier–Holland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSongwriterTeam Context triple: [Invictus Records, notableSongwriterTeam, Holland–Dozier–Holland]
-
A.
songwritingTeam
chosen
Indicates a collaborative relationship in which multiple individuals work together as a team to write songs.
-
B.
hasNotableLyricistTeam
Indicates that an entity is associated with a lyricist team that is recognized as notable or distinguished.
-
C.
notableSongwriterOn
Indicates that one entity is recognized as a notable songwriter contributing to or associated with another entity (such as a musical work or recording).
-
D.
hasComposerLyricistTeam
Indicates a relationship where a musical work is associated with a specific team that jointly fulfills the roles of composer and lyricist.
-
E.
notableLyricist
Indicates that the subject is a lyricist who is particularly distinguished or well-known for their work.
- 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a419deaf65c8190bac7954b136c1141 |
completed | June 28, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:29 p.m.