Triple
T35053656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emotion Engine |
E1011399
|
entity |
| Predicate | graphicsInterfaceBandwidth |
P170871
|
FINISHED |
| Object | 1.2 GB/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: 1.2 GB/s | Statement: [Emotion Engine, graphicsInterfaceBandwidth, 1.2 GB/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: graphicsInterfaceBandwidth Context triple: [Emotion Engine, graphicsInterfaceBandwidth, 1.2 GB/s]
-
A.
networkBand
Indicates the specific frequency band or range within a network over which communication or data transmission occurs.
-
B.
supportsBandwidths
Indicates that an entity is compatible with or can operate using the specified range or set of bandwidth values.
-
C.
topBandWidth
chosen
Indicates the maximum data transfer capacity or throughput available at the upper limit of a connection, channel, or system.
-
D.
hasGainBandwidthProductTypical
Indicates that an entity has a specified typical value for its gain–bandwidth product, describing the standard frequency–gain performance characteristic.
-
E.
bandwidthCharacteristic
Indicates the relationship specifying the bandwidth-related properties or constraints associated with a connection, link, or communication channel.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f785cfbdc081908499d3d5341ee3c3 |
completed | May 3, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.