Triple
T19611401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detroit techno |
E470737
|
entity |
| Predicate | emergedFromScene |
P1257
|
FINISHED |
| Object | Detroit high school party 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: Detroit high school party scene | Statement: [Detroit techno, emergedFromScene, Detroit high school party scene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emergedFromScene Context triple: [Detroit techno, emergedFromScene, Detroit high school party scene]
-
A.
emergedFrom
chosen
Indicates that one entity originated, arose, or came forth from another entity or source.
-
B.
emergesAt
Indicates that something comes into existence, becomes visible, or starts to be apparent at a specific time, place, or condition.
-
C.
emergesAs
Indicates that one entity comes to be recognized, develops, or appears in the role, form, or status of another entity over time.
-
D.
emergedInContext
Indicates that something came into existence, became apparent, or developed within a specific situation, environment, or set of circumstances.
-
E.
emergedWith
Indicates that one entity came forth, appeared, or became visible at the same time and in association with 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640cb180c8190ba96ffb69c24e2e1 |
completed | April 20, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.