Triple
T15914189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goner Records |
E385926
|
entity |
| Predicate | focusesOnScene |
P31
|
FINISHED |
| Object | Memphis garage rock 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: Memphis garage rock scene | Statement: [Goner Records, focusesOnScene, Memphis garage rock scene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnScene Context triple: [Goner Records, focusesOnScene, Memphis garage rock scene]
-
A.
focusesOn
chosen
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
B.
focusOf
Indicates that one entity is the primary subject, target, or center of attention, activity, or interest for another entity.
-
C.
focusesBy
Indicates that one entity directs its attention, effort, or emphasis toward another entity or specific aspect of it.
-
D.
focusesOnContentFrom
Indicates that an entity’s attention, activity, or operations are directed toward the content produced by another entity.
-
E.
centralScene
Indicates that one scene functions as the main or focal scene within a larger narrative, sequence, or composition.
- 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:52 a.m.