Triple
T16207861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Headshot |
E393373
|
entity |
| Predicate | primaryGenreRegion |
P118703
|
FINISHED |
| Object | New York hip hop |
—
|
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: New York hip hop | Statement: [Headshot, primaryGenreRegion, New York hip hop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryGenreRegion Context triple: [Headshot, primaryGenreRegion, New York hip hop]
-
A.
hasPrimaryGenreRegion
chosen
Indicates that an entity’s main or dominant genre is associated with a particular geographic region.
-
B.
musicGenreRegion
Indicates the association between a music genre and the geographic region where it originates, is most prevalent, or is culturally significant.
-
C.
hasGenreOrigin
Indicates that a genre originates from, or has its roots in, a particular source, place, culture, or tradition.
-
D.
primaryRegionOfPopularity
Indicates the geographic region where something is most widely used, favored, or popular compared to other regions.
-
E.
primarySourceGenre
Indicates the genre or type of creative work that serves as the primary source for something (e.g., an adaptation, derivative work, or related resource).
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e22710ef2c8190a8d7b9fb1666816c |
completed | April 17, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.