Triple
T29070112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sexy Movimiento |
E735790
|
entity |
| Predicate | musicalDuoArtist |
P177746
|
FINISHED |
| Object | Wisin & Yandel |
—
|
NE NERFINISHED |
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: Wisin & Yandel | Statement: [Sexy Movimiento, musicalDuoArtist, Wisin & Yandel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicalDuoArtist Context triple: [Sexy Movimiento, musicalDuoArtist, Wisin & Yandel]
-
A.
hasNotablePerformerDuo
Indicates that the subject has a notable performing duo associated with it, such as a well-known pair of artists or entertainers who perform together.
-
B.
fromArtistDuo
chosen
Indicates that something originates from or is created by a pair of artists working together as a duo.
-
C.
artistDuoMember
Indicates that one entity is a member of a specific artist duo.
-
D.
performedByDuoFrom
Indicates that an action or performance is carried out by a duo whose origin or affiliation is from a specified place or source.
-
E.
partnerInMusicDuoWith
Indicates that two entities are members of the same musical duo, performing together as a two-person act.
- 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_69f077e9b0a48190bb79548279cb7f64 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 28, 2026, 10:19 a.m.