Triple
T16380561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bang Records |
E397793
|
entity |
| Predicate | notableSingleFormat |
P14840
|
FINISHED |
| Object | 7-inch single |
—
|
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: 7-inch single | Statement: [Bang Records, notableSingleFormat, 7-inch single]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSingleFormat Context triple: [Bang Records, notableSingleFormat, 7-inch single]
-
A.
notableFormat
chosen
Indicates that something is particularly recognized or distinguished for being in a specific format.
-
B.
notableRecordingMedium
Indicates that an entity is notably recorded, documented, or expressed using a particular medium or format.
-
C.
notableSingle
Indicates that the subject is particularly recognized or distinguished for one specific, individual instance (such as a single work, event, or achievement).
-
D.
presentedInFormat
Indicates that something is expressed, delivered, or made available using a particular format or representation.
-
E.
notableEdition
Indicates that a particular edition or version of a work is especially significant or noteworthy in relation to that work.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e319db5b648190a8fca23518a1fb39 |
completed | April 18, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.