Triple
T28190015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Take It to the Head |
E716276
|
entity |
| Predicate | hasCollaborativeLineup |
P63184
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Take It to the Head, hasCollaborativeLineup, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollaborativeLineup Context triple: [Take It to the Head, hasCollaborativeLineup, true]
-
A.
hasBandmates
Indicates that two or more individuals are members of the same musical band or group at the same time.
-
B.
notableLineup
chosen
Indicates that an entity is recognized as part of a particularly significant or distinguished group, roster, or cast associated with another entity.
-
C.
hasCollaboratedIn
Indicates that two or more entities have worked together on a shared project, task, or activity.
-
D.
musicalCollaborator
Indicates a relationship where two or more entities work together in creating, performing, or producing music.
-
E.
hasComposerLyricistTeam
Indicates a relationship where a musical work is associated with a specific team that jointly fulfills the roles of composer and lyricist.
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69ff84202eb081908ae21a54a4414d68 |
completed | May 9, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69ff833065e4819098579129d4ee17d3 |
completed | May 9, 2026, 6:55 p.m. |
Created at: April 27, 2026, 10:25 p.m.