Triple
T28430650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mainstream Records |
E715117
|
entity |
| Predicate | issuedFormat |
P5128
|
FINISHED |
| Object | LP |
—
|
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: LP | Statement: [Mainstream Records, issuedFormat, LP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuedFormat Context triple: [Mainstream Records, issuedFormat, LP]
-
A.
presentedInFormat
Indicates that something is expressed, delivered, or made available using a particular format or representation.
-
B.
printedInFormat
Indicates that something has been produced or output using a specified printing format or layout.
-
C.
format
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
D.
publishedEdition
Indicates that one entity is a specific edition or version that has been formally published of another work or resource.
-
E.
hasPublishingFormat
chosen
Indicates that an entity is associated with a specific format or medium in which it is published or made publicly available.
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 28, 2026, 1:39 a.m.