Triple
T18634546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capitol 5112 |
E455508
|
entity |
| Predicate | rpm |
P132478
|
FINISHED |
| Object | 45 rpm |
—
|
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: 45 rpm | Statement: [Capitol 5112, rpm, 45 rpm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rpm Context triple: [Capitol 5112, rpm, 45 rpm]
-
A.
EPRelease
Indicates the event or relationship in which a musical artist or entity releases an EP (extended play record) into public distribution.
-
B.
distributionPackage
Indicates that one entity is a package or bundle used to distribute another entity (such as software, content, or resources).
-
C.
ROM
Indicates a relationship where one entity is a Read-Only Memory component or resource associated with another entity (such as a device, system, or module).
-
D.
packageNameOnRedHat
Indicates that a given software package has the specified package name in Red Hat–based distributions.
-
E.
bundle
Indicates that multiple items are grouped or packaged together as a single combined unit or offering.
- F. None of above. chosen
Provenance (4 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54fc74d208190bfda63b5b0b160cd |
completed | April 19, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e485f5d1588190b44f31cbc54c0a9d |
completed | April 19, 2026, 7:36 a.m. |
Created at: April 10, 2026, 11:46 a.m.