Triple
T97953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vitaphone |
E1974
|
entity |
| Predicate | soundRecordingSpeed |
P3511
|
FINISHED |
| Object | 33 1⁄3 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: 33 1⁄3 rpm | Statement: [Vitaphone, soundRecordingSpeed, 33 1⁄3 rpm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soundRecordingSpeed Context triple: [Vitaphone, soundRecordingSpeed, 33 1⁄3 rpm]
-
A.
frequency
Indicates how often an event, action, or relationship occurs within a given period or context.
-
B.
hasAverageSurfaceSpeed
Indicates the typical or mean speed at which something moves across a surface over a given period or distance.
-
C.
dataRate
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
D.
tempo
Indicates the speed or pace at which an action, process, or sequence unfolds over time.
-
E.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
- 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a24feef1b08190bb9525f71cce053e |
completed | Feb. 28, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69a24ebe7b1c8190a6bfbf31dc7c7f07 |
completed | Feb. 28, 2026, 2:11 a.m. |
| PDg | Predicate description generation | batch_69a24f4b4658819087902414959161fb |
completed | Feb. 28, 2026, 2:13 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.