Triple
T21723277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Do (Cherish You) |
E536213
|
entity |
| Predicate | associatedWithArtistType |
P145096
|
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: [I Do (Cherish You), associatedWithArtistType, boy band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithArtistType Context triple: [I Do (Cherish You), associatedWithArtistType, boy band]
-
A.
associatedWithArtistGroup
Indicates that an entity has a relationship or connection with a particular artist group or collective.
-
B.
associatedWithArtistSeries
Indicates a relationship where something is connected or linked to a particular artist series.
-
C.
associatedWithPerformer
Indicates a relationship in which something (such as a work, event, or role) is connected or linked to a specific performer.
-
D.
associatedWithArtistMovement
Indicates that an entity has a connection or affiliation with a particular artistic movement or style.
-
E.
associatedWithArtistHeritage
Indicates a relationship where an entity is connected to, derived from, or meaningfully linked with an artist’s cultural, ethnic, or historical heritage.
- F. None of above. chosen
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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd97150c08190861bdc35416665a9 |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:48 p.m.