Triple
T7715250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Modern Records |
E174862
|
entity |
| Predicate | releasedFormat |
P3286
|
FINISHED |
| Object | 78 rpm records |
—
|
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: 78 rpm records | Statement: [Modern Records, releasedFormat, 78 rpm records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releasedFormat Context triple: [Modern Records, releasedFormat, 78 rpm records]
-
A.
releaseType
chosen
Indicates the kind or category of a release event or version associated with an entity.
-
B.
releasedInsteadOf
Indicates that one entity was released in place of, or as a substitute for, another entity that was not released.
-
C.
fullyReleasedAs
Indicates that something has been completely made available or published in its final, unrestricted form.
-
D.
subsequentReleaseFormat
Indicates that one media release is issued in a different format that chronologically follows an earlier release of the same content.
-
E.
releasedFor
Indicates that something has been made available or authorized for public use, distribution, or access.
- 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_69c6995c463c8190a14458036249d419 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702ebb7448190ae8d47fe0cbb0907 |
completed | March 27, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69c701683dec8190be9861e592aa8ce0 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:04 p.m.