Triple
T28077200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roscoe Dash 2.0 |
E709575
|
entity |
| Predicate | isFromScene |
P22079
|
FINISHED |
| Object | Atlanta hip hop scene |
—
|
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: Atlanta hip hop scene | Statement: [Roscoe Dash 2.0, isFromScene, Atlanta hip hop scene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFromScene Context triple: [Roscoe Dash 2.0, isFromScene, Atlanta hip hop scene]
-
A.
hasInfluenceFromScene
chosen
Indicates that something is affected, shaped, or guided by the characteristics or context of a particular scene.
-
B.
isPivotalSceneFor
Indicates that a particular scene plays a crucial or decisive role in the development or outcome of another entity, such as a story, event, or narrative arc.
-
C.
isAssociatedWithLabelScene
Indicates that an entity is connected to or involved with a particular labeled scene or scene annotation.
-
D.
containsScene
Indicates that one entity (typically a media item or narrative work) includes or features a particular scene as part of its content.
-
E.
featuresSceneFrom
Indicates that one entity (such as a work or media item) includes or presents a particular scene taken from another entity.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 8:49 p.m.