Triple
T5388601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ten Crack Commandments |
E120264
|
entity |
| Predicate | hasCanonicalStatusInGenre |
P62957
|
FINISHED |
| Object | classic hip hop track |
—
|
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: classic hip hop track | Statement: [Ten Crack Commandments, hasCanonicalStatusInGenre, classic hip hop track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonicalStatusInGenre Context triple: [Ten Crack Commandments, hasCanonicalStatusInGenre, classic hip hop track]
-
A.
hasGenreInRoles
Indicates that an entity participates in roles associated with a particular genre or set of genres.
-
B.
hasGenreScope
Indicates that something (such as a work, collection, or classification) is limited to, defined by, or applicable within a particular genre or set of genres.
-
C.
isScoreForGenre
Indicates that a given score or rating is specifically associated with a particular genre.
-
D.
hasGenreStrength
Indicates that something possesses a particular intensity or degree of emphasis associated with a specific genre.
-
E.
hasGenreList
Indicates that an entity is associated with a set or list of genres that categorize or describe it.
- 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd871573b48190aa60871be56847ae |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd853005088190b1b092a9beb090b2 |
completed | March 20, 2026, 5:34 p.m. |
Created at: March 20, 2026, 2:04 p.m.