Triple
T20402403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capitol Records LP catalog |
E500369
|
entity |
| Predicate | formatDescribed |
P130
|
FINISHED |
| Object | 12-inch vinyl record |
—
|
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: 12-inch vinyl record | Statement: [Capitol Records LP catalog, formatDescribed, 12-inch vinyl record]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatDescribed Context triple: [Capitol Records LP catalog, formatDescribed, 12-inch vinyl record]
-
A.
styleDescribedAs
Indicates that the manner, aesthetic, or mode of something is characterized or labeled using a particular style description.
-
B.
format
chosen
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
C.
formatMayChange
Indicates that the format or structure of something is subject to modification and may not remain consistent over time.
-
D.
describesForm
Indicates that one entity provides a description, specification, or characterization of the form or structure of another entity.
-
E.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
- 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_69e0b4a81bec8190b69adfdc1336a015 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6798fc3b88190a372c34102bfaa6f |
completed | April 20, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:29 a.m.