Triple
T2755305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Four Tops |
E61085
|
entity |
| Predicate | vocalTypeOfMembers |
P24750
|
FINISHED |
| Object | tenor and baritone male voices |
—
|
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: tenor and baritone male voices | Statement: [The Four Tops, vocalTypeOfMembers, tenor and baritone male voices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalTypeOfMembers Context triple: [The Four Tops, vocalTypeOfMembers, tenor and baritone male voices]
-
A.
hasFemaleVocalist
Indicates that the subject entity features or includes at least one female vocalist as a performer.
-
B.
vocalRequirement
Indicates that a particular action, role, or participation involves a specified need or condition related to vocal use, such as speaking or singing.
-
C.
hasVocalPartInMovement
Indicates that a vocal part is present and participates in a specific movement of a larger musical work.
-
D.
vocalRange
Indicates the span of pitches or notes that an entity (such as a singer or instrument) is capable of producing.
-
E.
hasVocalRangeDescription
chosen
Indicates that an entity is associated with a textual description of its vocal range or vocal capabilities.
- 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_69ab4b7a85bc819094a349b84beb1f2c |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb718f4c8190bfc34c6597163ebc |
completed | March 7, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69abd82d005c81908a1ac7a1313c6d88 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.