Triple
T25757125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coco Montoya |
E648630
|
entity |
| Predicate | activeAsSoloArtist |
P32621
|
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: [Coco Montoya, activeAsSoloArtist, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeAsSoloArtist Context triple: [Coco Montoya, activeAsSoloArtist, true]
-
A.
isFromArtistSoloCareer
Indicates that the work or contribution originates from an artist’s solo career rather than from a group or band they are associated with.
-
B.
madeArtistASoloStar
Indicates that one entity was responsible for establishing another artist as a solo star, distinct from any group or collaborative identity.
-
C.
hasSoloAlbum
Indicates that an individual has released at least one music album as a solo artist, separate from any group or band projects.
-
D.
isSoloDebutOf
Indicates that an event, work, or performance is the first solo appearance or release of a particular individual.
-
E.
hasSoloCareer
chosen
Indicates that an individual has pursued a musical or artistic career independently, separate from any group or band affiliations.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 22, 2026, 4:42 a.m.