Triple
T37990661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal Media Disc |
E947814
|
entity |
| Predicate | readingSpeed |
P140228
|
FINISHED |
| Object | up to 11 Mbps (approximate PSP read rate) |
—
|
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: up to 11 Mbps (approximate PSP read rate) | Statement: [Universal Media Disc, readingSpeed, up to 11 Mbps (approximate PSP read rate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: readingSpeed Context triple: [Universal Media Disc, readingSpeed, up to 11 Mbps (approximate PSP read rate)]
-
A.
readSpeed
chosen
Indicates the rate at which an entity reads or processes written material.
-
B.
readingTime
Indicates the duration or amount of time an entity spends (or is expected to spend) reading another entity.
-
C.
writingSpeed
Indicates the rate at which an entity produces written content over a given period of time.
-
D.
timeRequiredToRead
Indicates the amount of time needed for an entity (such as a person) to read a given item or content.
-
E.
readingOf
Indicates that one entity is an interpretation, measurement, or recorded value derived from another entity.
- 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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:20 p.m.