Triple
T13940636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pretty Boy |
E335237
|
entity |
| Predicate | hasPerformerMemberOf |
P47574
|
FINISHED |
| Object | boy band |
—
|
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: boy band | Statement: [Pretty Boy, hasPerformerMemberOf, boy band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformerMemberOf Context triple: [Pretty Boy, hasPerformerMemberOf, boy band]
-
A.
mainPerformerMemberOf
Indicates that the primary performer in an event or work is a member of a specified group, band, ensemble, or organization.
-
B.
performerMemberOf
chosen
Indicates that a performer is a member of, or affiliated with, a particular group, organization, or ensemble.
-
C.
associatedWithPerformer
Indicates a relationship in which something (such as a work, event, or role) is connected or linked to a specific performer.
-
D.
recordingArtistMemberOf
Indicates that a recording artist is a member of, or affiliated with, a particular musical group, band, or ensemble.
-
E.
hasPerformerGroupType
Indicates that an entity is associated with a performer group of a specific type or category (e.g., band, choir, ensemble).
- 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_69d81c6081b88190b53e317c3370c8fe |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2cf6e29881908ddb8efca9a456a3 |
completed | April 14, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69dbc873052c8190b33ff7f7c5a4e7ee |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:17 p.m.