Triple
T27947248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curriculum Vitae |
E703316
|
entity |
| Predicate | featuresArtistRosterOf |
P195631
|
FINISHED |
| Object | Mo' Hits Records |
—
|
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: Mo' Hits Records | Statement: [Curriculum Vitae, featuresArtistRosterOf, Mo' Hits Records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresArtistRosterOf Context triple: [Curriculum Vitae, featuresArtistRosterOf, Mo' Hits Records]
-
A.
primaryArtistRoster
Indicates that an artist is a main or featured member of an entity’s official artist roster.
-
B.
notableArtistRosterIncludes
Indicates that a notable artist is included as part of an entity’s recognized or distinguished roster of artists.
-
C.
featuresArtistFromRegion
Indicates that something includes or highlights an artist whose origin or affiliation is with a specified geographic region.
-
D.
artistsFrom
Indicates that one or more artists originate from, are associated with, or come from a specified place or region.
-
E.
featuresBandMembersOf
Indicates a relationship where something (such as a work, event, or item) includes or highlights the members of a particular band.
- 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_69ef840c8b2c8190946ae9522774ba51 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
| PDg | Predicate description generation | batch_69fddd364c1481908794c9d423bdc2d7 |
completed | May 8, 2026, 12:55 p.m. |
Created at: April 27, 2026, 7:23 p.m.