Triple
T3778158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dreamcast |
E83356
|
entity |
| Predicate | modemSpeed |
P1376
|
FINISHED |
| Object | 56 kbit/s |
—
|
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: 56 kbit/s | Statement: [Dreamcast, modemSpeed, 56 kbit/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modemSpeed Context triple: [Dreamcast, modemSpeed, 56 kbit/s]
-
A.
supportsBusSpeed
Indicates that one entity is capable of operating at, or is compatible with, a specified bus communication speed of another entity.
-
B.
supportsBandwidths
Indicates that an entity is compatible with or can operate using the specified range or set of bandwidth values.
-
C.
dataRate
chosen
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
D.
duplexMode
Indicates whether a communication link or device operates in half-duplex or full-duplex mode, defining if data can flow in one or both directions simultaneously.
-
E.
integratedModemVendor
Indicates that one entity is the vendor or supplier of the integrated modem used within another entity (such as a device or system).
- 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_69ad8b235e608190b5a2b1d1bfcef50b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc78173081908b230017834cdf9e |
completed | March 8, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69adc050cc5c81909d9855f866f3c26d |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:36 p.m.