Triple
T3121753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US Alternative Songs chart |
E65199
|
entity |
| Predicate | targetFormat |
P38824
|
FINISHED |
| Object | alternative rock radio format |
—
|
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: alternative rock radio format | Statement: [US Alternative Songs chart, targetFormat, alternative rock radio format]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetFormat Context triple: [US Alternative Songs chart, targetFormat, alternative rock radio format]
-
A.
packageFormat
Indicates the format or type in which a package is structured, encoded, or delivered.
-
B.
format
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
C.
operatesInFormat
chosen
Indicates that an entity functions, performs its role, or is carried out using a specified format.
-
D.
projectionFormat
Indicates the specific technical format or method used to project visual content (such as film or digital media) onto a display surface.
-
E.
includeFormat
Indicates that one entity contains or specifies the format or representation type of 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_69ad8580c72481909672d37acf647893 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada52ab05c819088204bbb608c837c |
completed | March 8, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69ad9df455088190940ad04419772dc8 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.